> As i have said before I you'd be better off accepting that SQL servers are
> not ISAM's
> and embrace the changes it will require, not fight them
Gotta agree here - I've only ever used explicit locking once - in a paradox
app, where I had to lock the record or another paradox app would clobber my
data before I could write it properly. It was a fix for a specific problem,
not a specific solution.
Take a look at things like "UpdateWhereAll" and "UpdateWhereChanged" - ie,
rather than generating something like
update <table>
set <all the fields>
where
key = <value>
it does:
update <table>
set <all the fields or some of the fields>
where
key = <value> and changedField1 = <oldfield1value> and <etc>
or it checks all the fields - ie, you can't clobber someone elses changes
(but you can write to other fields they havn't changed), or you can't
clobber a record someone else has changed at all. It gets the same results
as locking, pretty much, without the overhead. Look at the bottom of
T<xx>Query - UpdateMode I think its called.
N
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
