Hi!

ADO use new principles of data updating and management of the conflicts in the multi-user environment. It has a set of field properties that are similar to VFP functions OldVal() and CurVal(), comparing which you can determine if data on the server or database are changed by another user. So when data saved, you run a routine and say user that some fields already changed by another user, maybe even show new values, then ask if user want to overwrite changes. I did made similar routine in the past (3 years ago) and it worked very well.

There are no locking in ADO, as far as I know.

HTH.

>First, Thanks to all who have answered my many questions on ADO. As ypu
>probably figured, I'm well into a VFP project using ADO.
>
>I'v been developing a VFP COM object which handles all the ADO stuff. This
>DLL is then instantiated inside a business object, which in turn is
>instantiated by a GUI which runs various processes. So far, all is well.
>
>The question today I have is this; What are the pro's and con's of using
>ADO in a VFP Mult-User environment? How do handle comflicts? How do ensure
>a record is locked when I want it locked?
>
>Thanks again for all the help
>
>Kevin