>I have an application where the newid() when hit at the same time by two users gives each use the same value. It appears to be a buffering issue with the rlock(). Any suggestions?
>
>That's strange. I'm currently working with a shop that may have up to 75 users adding records and this doesn't happen to us.
>
>What exactly are you doing to determine that NEWID() gives you identical Unique ID's?

There is a detail record(s) being created at the same time as the master record this detail record(s) contain diffrent customer identification and the same master record id value.

>
>Is it a possibility that your records in the ID Table are currently generating ID's that already exist? Check the PK on one of tables that uses NEWID() and compare it to what's in the ID Table.

Yes that is the problem the id generated by the newid() is being picked up by the other workstation at the same time. But the way that newid() in MM is written this should not be the problem.

We have researched this down to what we think the problem is that the ID table is not being updated as to the new value. Now the question is how to insure that the value that was just placed in the value field of the ID table is seen by the other workstations.

Thanks
Jon