🚀 go-pugleaf

Using BDS2006, TADOQuery, MSSQL 2005 Express, MS SQLOLEDB.1 driver

I'm trying to see if I can make a TADOQuery to not get a concurrency 
error when I:

1) Select single row in App A
2) App B updates same row
3) App A then updates same row via TADOQuery::Edit() and ::Post() 
methods, but gets concurrency error (specifically "Row cannot be located 
for updating. Some values may have been changed since it was last read")

Ignoring the general issue of should I be doing this or not, does anyone 
know of a way to make App A still be able to overwrite the changes 
posted by App B without making App A reestablish position (i.e., issue 
another select statement)?

I've been playing around with the connection's IsolationLevel, the 
query's CursorType and LockType, but no luck.

Any suggestions?

Thanks,
Paul Rodden