>I'm using VB 6.0, DAO and optimistic locking.
>
>How do you handle update collision when saving modifications with Update? With an On Error? If so, what kind of error do I look for?
>
>TIA

You are right. You have to handle error using the "On Error Goto Somewhere" statement.

The most important errors you should check for are the following:
3260: Couldn't update, currently lock (can occur on Edit). Should not be a concern on Optimistic locking.
3186: Couldn't save, currently lock (can occur on Update).
3197: Data has changed, operation stopped (can occur on Edit and Update).
3167: Record is deleted (can occur on Edit and Update).