Can you give any specifics on which versions were used before the upgrade that caused these errors.   I want to be cautious in my test environments as well as production so any extra details you could provide would help tremendously.

thanks...

I'm afraid without tracking back through 1000's of lines of SQL code I can't easily tell where the problem is caused, and even then (since a fresh install would not have the problems) we've seen I cannot guarantee we would see the problem. I suspect that previous problem SQL may have been corrected subsequently, but left behind installations that have errors. To help with this going into the future, we do propose to provide a release that specifically tries to tackle these problems, we are expecting this to be version 5.0.3.

I personally would be suspicious of installations that started prior 3.3.8, because that is the basis the current team started to work from. So in theory an upgrade from a version that was installed at version 3.3.8 should be reliable. But if you started with an earlier version, there may be problems.

We have a version 5.0.2 in the works, which should beta very soon, and addresses the problems we have identified in the last week since 5.0.1 released, and will give a more reliable upgrade installs that started with versions prior to 3.3.8.

Hope this helps, please ask if you want to know more.

Cheers
Roger