Linking Tables

[Maquis]

Hi,
I posted this problem a couple of days ago, but I never received a solution, so I figured I would try once more before giving up.

I have a database which I have "locked down" so users cannot get to the design view of the database and wreck havoc there. If the users need to create custom reports and queries then they can create a blank database on their own and link to the tables in my database.

Here's the problem. I have a user who linked to the system tables in my database and messed them up. Arrrghhhh!!!!! (My users are very creative. If there is a way to destroy a database, they will find it!) X-)

Is it possible to prevent this? I want them to be able to link to the normal tables, but I don't want their grubby little fingers on the system tables.
Maq B-)
<insert witty signature here>

 

[Megahurtz]

During this process they should create local copies of the master tables and do their dammage there you might be able to make up some code on a form/other that forces them to do this. I assume you are using the switchboard to lock down the app and deny direct table/query/form manipulation. if not than you may want to look into that.

I would also keep a version on your database and back up often. This saved my Bacon too many times to count.

Anytime tables are linked via access regardless of format (sybase,oracle,etc) you have free reign over those linked tables. (that HURTZ!!)

 

[StewartGW]

Add a new user account in SQL Server, and set the Database Role Membership to 'Public' and 'db_DataReader'. Thereafter, go to the ODBC DSN Administrator and change the Login to the new user account on the client machine. The user will then only have read permission.

 

[Maquis]

Thanks for the suggestions, however I'm convinced at this point that there is no good answer to my dilemma.

Megahurtz, I want the users to be able to link and update the tables in my database. This is so they can run custom reports and possibly update the data if there isn't a way to do so through my forms. I'm not as concerned with the users messing up the data as I am with them messing up the design structure. They are responsible for all the data and it's integrity. I'm responsible for fixing the database when a form or query stops working. Backups aren't a problem. The database is on our company network so it's backed up every night.

Stewart, I'm using Access 97 to implement the database, not SQL server. If all that is possible in Access, then I'm afraid I don't know how to do it.

I guess my best answer really is not to worry about it and restore the database from backups if it happens again. I was just hoping there was a way to prevent it. Maq B-)
<insert witty signature here>

 

[StewartGW]

You through me with off with the words 'system tables'...I assume you were using SQL Server as a backend and Access as the front end to the data...Sorry!