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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

owning tables

Status
Not open for further replies.

chirpyform

Programmer
Jun 20, 2003
202
FR
I am using a multiuser database but I want it so that each user has a version of certain tables. This means that I have some tables that everyone can change at the same time. I want that each user connected at any moment given can take a copy of these tables and work seperately, the problem being that I don't want to have to create the extra tables for each user. I would like to have say 3 tables that Access gives ownership to each user ie each user sees his version of these tables and doesn't change the others version.
An other solution is to have the 3 tables and add a column userId and then I only change the records where userId = chirpy but I would prefer something more elegant. I saw that there was a table MSysObjects and I thought every user has their version of the relations window so surely there is an ownership option somewhere.

Any help gratefully received
Thanks
chirpy
 
Chirpy,

The most elegant solution I can think of is to have the database split between a user front-end and the shared data backend. The user-owned tables can reside as temporary tables on the front-end database and changes can be synched back to the back-end database as needed.

Mike Pastore

Hats off to (Roy) Harper
 
I agree with Mike Pastore--though I'm not sure you actually need to merge the changes back to the back end table.

The term "table owner" has a special meaning in Access that isn't related to what you need. In Access, the owner of a table is the user ID of the creator, or of another user ID to whom ownership was given by the creator or a previous owner. The owner has irrevocable administrative and usage permissions on the table, despite anything you might set up for permissions in the Access user-level security system.

In some database systems, different owners can have tables of the same name, because the table name is always qualified by an implicit or explicit owner ID. That's not true in Access, where a given database can only have one table with a given name. I'm explaining this so you won't waste time trying to base a solution on the Access ownership concept.

Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top