Hi dinkado

I cant offer a solution as I have been looking for one for ages.I see a large no of posts all over the web but no answers. Here is what I think, just dont know how to fix it.

I have the same problem as you indicate abouve, but i have another one that I think is the ACTAUL cause of the problem. I moved from an SQL 7 Environment into SQL 2003 and quess what. The SQL 7 and SQL 2003 default values differ. Namely collation. collation is the method that the server uses to Index Key values (I think). If your database was created using one form of collation and you move the database to another server using a differnt collation you are basically stuffed.

How this affected the above problem is somewhat of a mystery. It appears that when the stored procedure looks for a unique ModuleId, multiple ones match the malformed collation and u end up with what looks like duplicate id's when in fact they are different.

I simulated the upgrade of a module on my old server with the original collation and it went smoothly. Then I tried the same on the new server- bang it was blown. I tested this by trying to run some the the stored procedures directly and I got wierd results.

The big question now is trying to find someone that knows how to resolve the collation problem without shutting the damned working server offline - hell even that would help if i could find a way. I tried everything i can - gave up and recreated all the sites one by one over a few weeks.