I saw this thread ‘Please put ALL you bug reports in this thread’ in Groove discussion board.
I am not so sure about the list….
By company bas been desiging, developing, implementing and support solutions in Groove 2007 from the very first release and we have some insights into the inner working of Groove.
Thoughts on the list:
Form Designer errors from the forum ————————————
1. whenever you try to hide / show fields the entire form can get corrupted.
there is no error if this is done under script control
- I think you will find that this is caused by the incorrect initialisation of a date field.
—— Workaround - ALWAYS set a date field to a default or an initial value. NEVER leave the intial value empty.
——- I reported this to Msft a long time ago.
2. Changing the size allocated to a date fields, then trying to move the
field, causes the form to get totally corrupted
—— See item #1
3. creating groups in a tab then removing them kills the form
—— See item #1
4. adding more than one tab control to a form generates an error (non fatal f you remove the extra tab)
—— See item #1
5. Lookups created using the normal designer are much slower than the same ookup in a script. Also, combo boxes refresh each time a new value is picked p / added and this could be a few thousand.
—— Correct. I have written a workaround for this.
6. Forms can take many minutes to open, specially if there are self lookups sed and more than 5,000 entries in the form.
—— Correct. I have written a workaround for this but ensure you do not have to many sorts on any view. RULE #1 - More views less sorts!
I believe the current list of feature is:
Form and Form Designer errors
1. Date fields are incorrectly initialised - the workaround MUST be followed.
2. Lookups refresh each time a new value is picked - workaround available.
3. Lookups fail to be registered correctly and no values are returned when using (some) international keyboards.
4. Contact fields are not correctly initialised and are also field values cannot be deleted - workaround available.
5. When creating higlhy complex parent-child relationships (3 levels deep) propogation fails - workaround available. If you see this bug then you must be a serious Groove developer. See the Microsoft Time Recording tool coming out soon for an example of complex parent-child relationships….
6. When debugging using VS Groove stops responding - kill Groove and restart Groove. :=)
7. When you have one identity on two machines, when you exit the Designer.. you do not leave the designer…..! Spooky. The changes have been saved - you are just in in Groove never, never land. Press cancel and all will be ok.
8. DO NOT NOT NOT NOT NOT NOT - use duplicate field! It will corrupt the design datanase. DO NOT USE duplicate. UNDERSTAND!
9. DO NOT. DO NOT. Delete scripts from the left hand pane in the designer. Delete and add script from a for TAB. DO NOT delete from the left hand pane. UNDERSTAND! As you will be left in the Groove never, never land.
10. Do not use AUTOCREATE for all roles in a form and also set the TOOL permissions so GUESTS cannot create a form. This has a different result from leaving YOU in the Groove never, never land - it will leave the GUESTS in the Groove never, never land.
11.When designed views an error message is issued ‘view deleted..’ ‘sorted deleted’… Workaround. ALWAYS select the form(s) you wish to view prior to setting any sorts. If you do not - you will pay the price!
Groove files tool
1. Files security loop hole. See this
Summary
Groove has a few features - we just need to understand them, document them, reproduce them and work with Microsoft to understand and resolve them.
I will update this document, as and if I think of any others.