asked on

How to publish access 2007 application so users don't have access to tables and design mode

Hi,

I have created an access 2007 application to be run on a local shared drive for approximately 10 users. Everything is done and working fine but I would like to publish this application so that:

1. Users cannot have access to the main table where data is stored (unless provided a password)
2. Users cannot access design mode
3. The title page pops up every time the application opens ( title page has buttons which leads to all required forms)
4. Hide all forms and tables from user view.
5. Only one user is allowed to use the application at a time. If another user tries to access the application while in use, it should be locked.

Any help would be greatly appreciated.

Thanks!
Sarah

ASKER CERTIFIED SOLUTION

Jeffrey Coachman

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sarah_siu

ASKER

I can split this question into 5 different questions. I guess perhaps I'll address the "split database" first. I've read in your links how to split the database and why we should split.

So just a quick summary to ensure I understand. I pretty much link a separate encrypted database to the front end. The standalone database will be in a shared drive where all users have access. then the front end (forms,queries, reports, etc.) will be downloaded into the user's computer.

In this case, does this allow for multiple user entries at a time?

I am looking more so for one user at a time entry...

Jeffrey Coachman

<I can split this question into 5 different questions.>
I have implicitly agreed to help you with 2,3 and 4, so you can make a new Q for #1, and a new Q for #5
;-)

You first split the database.
Put the Backend (BE) (the DB with the tables only) on a shared drive on a Server
Put the Front End (FE) in a "Safe" location. (this is your "Golden/Reference" copy of the DB that you will make any modifications to), ...and to be sure, make a backup of this FE file...
;-)
Test the Front end db
Create the accde file (this will be the FE the users use)
Test the accde file
Copy the accde file to each users computer.
Test the FE at each users computer.

<In this case, does this allow for multiple user entries at a time? >
Yes.
<I am looking more so for one user at a time entry...>
Can I ask why?
This is something to be addressed when you post your "One user at a time " question.
If multiple computers need to access the DB (whether one at a time, or simultaneously), the DB needs to be split in this way.
I am sure another Expert can provide you with a system to only allow one user at a time in the database.

;-)

JeffCoachman

sarah_siu

ASKER

Thanks JeffCoachman. Actually, based on the links you sent me, I am able to do what I was looking to do. No need to split the questions. Have a great weekend!