kovan
Aug 14th, 2000, 01:00 PM
i havent gotten answer to this question anywhere so i might get it here
i got a access DB somewhere on a workstation on our network
lets say on Z:
this database has about 30-40 tables
i have built a application that will modify, read, delete
records from these tables in the db
What i like to happen is
NO user should access the same table at the same time
(dont know if this is a good thing or not)
at least i dont want 2 users to modify the same table at the same time
(i am not familiar with cursors and locking types, even thou i read so much about them, but i dont unrestand them)
and as far as ADO error capturing, i am not trying to catch any yet.
cus i dont know ho wi should
so what am asking is
if anyone know of an article somewhere the explains how the best way to go about building a multi user app, by setting different cursor types, locking, error handling, ect
i would greatly appreciated, thanks
or if you wanna put your .02 cents in a reply to this
still appreciated
thank you
i got a access DB somewhere on a workstation on our network
lets say on Z:
this database has about 30-40 tables
i have built a application that will modify, read, delete
records from these tables in the db
What i like to happen is
NO user should access the same table at the same time
(dont know if this is a good thing or not)
at least i dont want 2 users to modify the same table at the same time
(i am not familiar with cursors and locking types, even thou i read so much about them, but i dont unrestand them)
and as far as ADO error capturing, i am not trying to catch any yet.
cus i dont know ho wi should
so what am asking is
if anyone know of an article somewhere the explains how the best way to go about building a multi user app, by setting different cursor types, locking, error handling, ect
i would greatly appreciated, thanks
or if you wanna put your .02 cents in a reply to this
still appreciated
thank you