PDA

Click to See Complete Forum and Search --> : Damn Multi-User Apps.. HELP


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

JHausmann
Aug 15th, 2000, 11:53 AM
Add one last table to your database, that contains "username" and "Tablename". Then have your program add/delete entries from this table as needed and read this table before using any other. You'll need to consider how to respond to errors in the table (someone ctl-alt-deletes out of your program before it has a chance to update the table, for example).

kovan
Aug 15th, 2000, 12:01 PM
hmmm
made more lost then i was
all i want to do is know about different locking and cursors
for the db type i mentioned above in my last post..

JHausmann
Aug 15th, 2000, 12:10 PM
If you're going to use Access and you want to implement a locking scheme like you indicated, you'll need to create your own.

kovan
Aug 15th, 2000, 12:17 PM
thank you for your replies, most kind

i still am kinda lost
first time i written a standalone app is used by few pcs at the same time to access the same db

basically what am trying to do is avoid bad data in the database, and the crashing of the database

so if one user is editing a record,
i dont want another user to access that record at all
until the first user is done what he is doing

i just like to know if there is a article, tutorial somewhere in can read on this..

thankyou