It could perhaps cheat.
I don't know if this would work (or this is what it does).
Start transaction
update record using it's current records
(Do not close the transaction)
Let user make edits
Then update record again with changes.
Now commit the transaction.
Real horrible for a SQL engine to deal with (IB may be okay with it's
versioning engine), but it may have the effect of locking the record - hope
they don't have too many users.
Myles.
> -----Original Message-----
> From: Neven MacEwan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 15, 2000 1:35 PM
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: Locking Records
>
>
> Sandeep
>
> > It is possible to lock a record using FIB TDataset.
> > Table.LockRecord is used to lock a record. When the LockRecord
> > function is called an update query is executed.
>
> And what does this 'update query' do? All I was stating was that SQL
> does not expose the concept of record locking I'd be interested to
> find out what the FIB TDataset.Table.LockRecord actually did
>
> Neven
>
>
>
> --------------------------------------------------------------
> -------------
> 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"
>
---------------------------------------------------------------------------
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"
