I'm not "hyping" this book however I must say that .....
1. It provides the usual source code examples, but it more importantly...
2. Enlightens me as to what the ADO control is doing "behind the scenes"! 
Which so far has allowed me to better understand the ADO object.

----------------------------------------------------------------------
I don't have a technical issue which needs to be resolved but I would 
certainly appreciate any thoughts any one may have concerning the 
following:

Using .CursorLocation = adClientSide
      .LockType = adLockBatchOptimistic

These settings Enable the OLE DB Synchronization Service which then allows 
me to programmaticly determine why an Update failed.

Once an Update fails I currently see that I can give 3 options to provide 
to the user -

1. Save your data *except* for those fields whose .UnderlyingValue has 
changed, or;
2. Cancel the Update and loose all changes - (This is not a viable option 
to a user whom has just entered 3 pages of data!), or...;
3. Overwrite any fields another user has previously changed. (Which in my 
experience, the user will always opt for this option.)

I am able to display to the user the fields which have been changed by 
another user as well as the name of the user who changed them. However, 
again it has been my experience that a user will simply choose to override 
the 'changed' data.

Any other ideas as to responses I might provide to my user whom is 
attempting to save data to a table that has recently been update would be 
greatly appreciated.

Oh, and by the way, Locking the record upon entering an Edit status as most 
of the people do in my organization, is not an acceptable solution. I used 
this method back in the days of programming on Primes and DOS.

Thanking you in advance,
lance