Need Assistance developing code to secure a database over a network. 1

[StillLearning]

Let me set up the scenerio:<br>
I have two databases which are linked together. Database #1 contains tables and forms which are to be accessed by Administrative personnel. Database #2 contains linked tables from Database #1. What are my options for creating security on both databases without requiring users to become part of a workgroup file or setting a database password for each database. <br>
<br>
Currently, database #1 has a database password. However, when I try to access database #2, I get an error message that says it is looking for Database #1. In addition, my Supervisor, doesn't want to add users to workgroups. She suggest using VBA code to handle this security issue. What should I do?<br>
<br>
By the way, I am using Access 97.<br>
<br>
StillLearning

 

[WP]

Is your Supervisor an Access expert ?<br>
<br>
Does she not realise that the work group is fundemental to ACCESS security ?<br>
<br>
<p>Bill Paton<br><a href=mailto:wpaton@neptune400.co.uk>wpaton@neptune400.co.uk</a><br><a href=

http://www.neptune400.co.uk>www.neptune400.co.uk</a><br>

 

[elizabeth]

Perhaps if you learned the reason for her opposition to workgroups, there's some misunderstanding we could clear up. She may have only been exposed to very complex (or poorly implemented) security schemes, but simple ones are possible. Your alternative is reinventing the wheel.

 

[StillLearning]

In reference to WP and Elizabeth's response, My supervisor is a proficient Access User. The main issue at hand involves the knowledge level of the average user at my facility. She doesn't want them to be burdened with having to join workgroups.<br>
<br>
As of my posting I have found a way to embed the database password in the second database. Thus when the user opens the second database, the database password is sent and opens the first database. Then the desired table is linked to the second database for use.<br>
<br>
I agree, I felt like I was on a rollercoaster to nowhere. Thanks for your support.<br>
<br>

 

[elizabeth]

Just FYI, there are simple ways of having workgroups without the user having to know anything about them. One is to embed the workgroup in the command to launch the database, in an icon that the user needs to open that database.