Hi Mazi, I'm from the same company as Marten. If I may add my 2$c:
Just for background, we encountered the problem both in 1.87 and in 1.90+, build 9642. Our setup is IIS + MSSQL Server, PHP 5.2 and use the database driver 'mssql_n'. We upgraded one of the 1.87 versions here to 1.90+, manual instructions. So we can test on both.
Now - if we patch those existing surveys in de database, giving each group_order field a different integer, it seems to work well and we can add a group in both versions, the numbering goes well.
For the 1.90+ version I just tried this:
1. Create a new survey, got id 13687
- If I create a new suvery and start adding a group, I see that the first group_order entrry is set at "0":
CL-USER> (clsql:query "select * from lime_groups where sid=13687")
((46 13687 "First group" 0 "Test opmerking first group<br />" "en"))
("gid" "sid" "group_name" "group_order" "description" "language")
- Now, after adding a second group the same query:
CL-USER> (clsql:query "select * from lime_groups where sid=13687")
((46 13687 "First group" 0 "Test opmerking first group<br />" "en")
(47 13687 "Second group" 0 "Test remarks second group<br />" "en"))
("gid" "sid" "group_name" "group_order" "description" "language")
Now, with two groups at group_order "0", we cannot reorder those groups until we have adjusted them manually.
Hope this helps. Let me know if I can help in any way tracking this one down.
Best regards,
-Emile