Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multiple users w/o sharing data

Status
Not open for further replies.

DedCat

MIS
Oct 9, 2002
15
US
My db is used by several people. All data is in one master table. The table is used for a search engine, and has a check box field that when checked, that record is added to a 'que' form. if i have several users, all users find that all of the records they 'checked' are in the que, as well as all of the records 'checked' by all other current users. Even worse, if a new user opens the db, a marco runs removing all checks from the db, emptying the que form for all users.
Is there a way to make a new instance of the db when a new user opens it? I don't want this new copy to be saved. I know this is counter to what most people want from a multi user db, but it's what I'm looking for.
Thanks to all
 
How about editing the que table to add a username field?
 
I don't advise linking backend tables over a network unless traffic is slow, BUT: can you create a backend on the network (split the database) and distribute the front end to each of your users (each will need Access installed)?

I have great faith in fools; self-confidence my friends call it.
-Poe
 
so if i split the db, input on the table from one user won't affect the same table being used by another user?
 
We do something similar where I work. I use the file scripting object to copy the database (which is 50 megs) from a folder on the network to a folder on the users computer, when the user logs in. It takes about 5 seconds to copy on our network.
 
You can link the single network backend tables to each user's frontend and hope Access will handle concurrency issues. If there is a table with data exclusive to each user (queue table?), make it a local unlinked table on the frontend mdb - the data will only reflect that user's preferences while still having access thru linked tables to the information common to everyone. Not sure I am getting all the subleties of your issue here tho.
Trav4's idea works great too, but if you need data updated on the backend mdb (copied back to the source folder), it will only reflect data from the last user to copy it back.

I have great faith in fools; self-confidence my friends call it.
-Poe
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top