FORMS HELP NEEDED

[Groovespacecadet]

I am running Groove 2007. I have XP and Office 2003.

I have made a custom groove space. I have a problem that goes like this...

After a several sessions of being able to select fields and move them around
in the forms designer -- eventually I get errors every time I select a field
and press the arrow buttons to move it; or change the column number etc.

This is the error:
Script Engin
(Template=http://components.groove.net/Groove...eForms.GrooveForms_TPL&Version=5&Factory=Open, Component=PreviewControlCode) encountered an error:
Line: 739
Position: 9
Problem: the parameter is incorrect

Code:
(null)
HRESULT: --
Process: GROOVE.EXE
ThreadID: 2224

At first I can make the change, get the error, press OK. Publish the change
and it 'takes'. After awhile no love, and I can make the change (amidst all
the errors) preview the change in the sandbox, but once I publish, it's like
it didn't happen.

Very frustrating. Last time I just exported everything, made a new
workspace, imported everything...but now I have so many fields and so much
data that it's a real pain. I just want to move my fields around.

 

[Frances Selkirk [MSFT]]

You might want to try posting this question in the "Groove Forms Development"
forum.

 

[Groovespacecadet]

Just FYI -- Here is the workaround for the problem I encountered, since once
I found the right Groove guy, he was very helpful.

*** Problem Description ***
Script error when moving Groove forms field

In the Groove 2007 forms design client, you may encounter the below script
error.
This generally occurs when attempting to move the location of a field on the
form.


Groove Error

Script Engine
(Template=http://components.groove.net/Groove/Components/Root.osd
Package=net.groove.Groove.Tools.Business.GrooveForms.GrooveForms_TPL&Version=5&Facto
ry=Open, Component=PreviewControlCode) encountered an error:
Line:739
Position:9
Problem:The parameter is incorrect.

Code:
(null)
HRESULT: 0x80020009
Process: GROOVE.EXE (ID: 3840 (0x00000f00))

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Resolution *** Apr 5 2007 6:58AM

The root cause of the problem is:
When you add a date field to the form that has no initial value (blank) we
store
a
null value in the field. In the design client, you are previewing the form
as it
would display to the end user. The component we use to preview the form cannot
properly render the null valued date field resulting in the error.

To work around this error:
Do not use static blank date fields on the form while moving fields on the
form.



<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Resolution *** Apr 12 2007 12:07PM

Further testing: It appears this problem only occurs while in the designer and
attempting to move field locations on the form. As a workaround, I believe we
can
set date values to "today" until the layout is proper, then as a last step
change
the date to static.


-----THIS IS WHAT I DID ----

0) I duplicated the workspace as a precaution
1) I made new date fields with "today" as the value
2) I unchecked the old date fields (the ones that had initially had static
as the 'initial value')
3) I moved the new date fields to the right place (the error messages did
not appear)
4) I entered all the new dates in the new date fields, using my duplicated
workspace to check (also, the view still showed the old values, even though I
unchecked the old fields in the view)
5) changed all the date fields back to 'static' for initial value, once I
have them positioned

Now, when I need to move a field around -- or add ANY field and move/alter
it (which will happen a lot at the beginning)

1) check if there is a date field in the preview window (if it's in a tab
behind what i am looking at, it seems to be no problem)
2) if so, go in and change the 'initial value' to today (haven't tested if I
have to publish this, or just use the sandbox -- i think the sandbox is
enough)
3) move my field around/alter as needed. The error should not appear, if it
does, it's because there is a date field in the preview with a static initial
value
4) once i get everything the way I want, i change the 'initial values' back
to static

it's a pain, but it seems to work for now. I did get a couple other weird
errors -- at one point, after I changed the initial values in the fields back
to static, could not save the change in the form designer (save button
greyed out)...but I made a different, unrelated change (deleted a random
field I did not need and had unchecked) and it un-greyed the save button and
all was fine.