I'm gonna agree with Alexandre on this one ... you might need to use transactions.

~~Bonnie



>>Something with your parameters maybe?
>
>I think I know what is causing this.
>
>On that particular page, and only in that particular page in the entire application, at the end there is a SQLUpdate() to update a counter on the record. For some kind of reason, since I put that in there, this is happening occasionnaly. Not only does it happen on the SQLUpdate() command, but it can also happen in other SQL exec I have in the same page that are trying to pull the record from the table. It seems the update is applying or trying to apply a lock. When a read is being done, this could cause that reaction.
>
>What would you recommend as a design approach to bullet proof the update on that particular record without affecting the next update which could happen at the same time or any SQL exec command that could try to pull the same record?