ADO update visability between workstations

Post by **nageswaragunupudi** » Mon Jun 25, 2007 4:47 pm

I just checked on MSSQL server with a two column table. Resync of current row is working fine, after a different usr from a different workstation modifed the data through other frontend. No need to touch properties. ( do not modify the uniquely indexed column values). Please try again with some other simple table with atleast one unique index.

Rick Lipkin · Post by **Rick Lipkin** » Mon Jun 25, 2007 5:58 pm

Please try again with some other simple table with atleast one unique index

Per your previous post .. as you suspected .. asigning the resync properties did not work ..

Interesting .. I do not have any indexes .. none at all .. perhaps this is the reason it is failing.

Rick Lipkin

Rick Lipkin · Post by **Rick Lipkin** » Mon Jun 25, 2007 7:59 pm

SUCCESS!!!!!!!!!!!!!!

For the oRs:ReSync( 1,2 ) option to work .. you MUST have a PRIMARY KEY set and NOT NULL checked. No other changes to the syntax need to be made.

ReSync() works perfectically and will update the visability of a changed record to a local cached recordset !

Thank you !!

Rick Lipkin

Post by **nageswaragunupudi** » Tue Jun 26, 2007 4:27 am

In future, if you get any ADO feature not working, put a standard routine to show the last ADO Error after CATCH. ADO Connection object contains an Errors collection. Last item of the Errors collection is the recent Error Object. Error object has these properties: Description, NativeError, Number, Source, SQL State, HelpContext, HelpFile.

If we write a generic routine to show ADO last error and put it after each CATCH statement, we know what to do without losing much time.