> ps. MS Access doesn't support row-locking, only page-locking. If you want
to
> use row-locking you have to adjust the size of a record to fit exactly one
a
> page.

> "Egdif" <ben.fi...@stylusnet.com> schreef in bericht
> news:0h8V5.12288$Bh.81379@NewsReader...
> > I'm having problems using pessimistic locking on an Access 2000 .mdb
file
> > using ADO 2.5 and TADOTable.  I'm writing a multi-user system whose
client
> > applications all reference the .mdb file and the system.mdw in a shared
> > directory an NT Server 4 system. I've set the "Jet OLEDB:Database
Locking
> > Mode" provider specific property to 1 (which denotes row-level locking).
> I
> > am assuming that like TTable with BDE, putting a dataset into edit mode
> will
> > create a lock for that record.  Is this right?

> This is probably a stupid question.  I know what a record is but what do
you
> mean when you talk about page? or is there some FAQ that I should be
> reading.

> Many Thanks,

> Don

> "M.H. Avegaart" <avegaartNOS...@mccomm.nl> wrote in message
> news:9052s3$gdt$1@porthos.nl.uu.net...
> > Only if you are using a server-side cursor.

> > ps. MS Access doesn't support row-locking, only page-locking. If you
want
> to
> > use row-locking you have to adjust the size of a record to fit exactly
one
> a
> > page.

> > "Egdif" <ben.fi...@stylusnet.com> schreef in bericht
> > news:0h8V5.12288$Bh.81379@NewsReader...
> > > I'm having problems using pessimistic locking on an Access 2000 .mdb
> file
> > > using ADO 2.5 and TADOTable.  I'm writing a multi-user system whose
> client
> > > applications all reference the .mdb file and the system.mdw in a
shared
> > > directory an NT Server 4 system. I've set the "Jet OLEDB:Database
> Locking
> > > Mode" provider specific property to 1 (which denotes row-level
locking).
> > I
> > > am assuming that like TTable with BDE, putting a dataset into edit
mode
> > will
> > > create a lock for that record.  Is this right?