My client NOW thinks PESS ROW BUFF may be acceptable and so I am trying to develop a demo for him to see the interactions.

The prob is that if I set the my tables to #2-PESSIMISTIC ROW BUFFERING and I try to edit a field that is being edited by someone else my ON ERROR routine correctly detects error()=109 and pops up the my desired message BUT after I click OK on my message, the executable QUIT's. I have no code telling it to QUIT and all of my other ERROR() routine works w/o prob. Why does it Quit?

I am now at 3 hours playing with this and reading docs (since yesterday) and I think I must have just missed something obvious.

Ideas??

>>Ian,
>>
>>Why not just use pessimistic buffering, it does what you want automatically wihtout any work.
>
>The only problem with that suggestion is that it requires the first user to actually make a change to the record to lock it. If user one retrieves a record, gets up and goes potty before making a change, a 2nd user can retrieve the record and modify it. I started a thread regarding RLOCK several months back and also decided that buffering was of no use due to the above situation. The person who I was researching this for could not accept that the above might happen. He wrote the app without buffering and mapped class properties to the forms performing his own locking and without buffering.
>
>Steve