By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,264 Members | 1,087 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,264 IT Pros & Developers. It's quick & easy.

Access 2003: Distributing App

P: 24
Hi Guys,

I just complicated my database and I wanted to know what is the best practice for staff to access the APP. I have split my DB in 2. The back end stores the data and the front end is the App. The database will be placed on a network drive. In my DB I have 4 different forms, there are 4 different staff using the DB. Each have different task to do which is why I had to create different forms. The best way I thought for distributing the app is copy the App to the staff desktop and then go into Tools Ė Startup. I was going to select the form they need and of course uncheck certain boxes to make sure they canít access anything else.

I canít think of any other way to distribute the App. If anyone has any other suggestions please let me know. Thank you for all input.
Mar 12 '07 #1
Share this Question
Share on Google+
4 Replies


MMcCarthy
Expert Mod 10K+
P: 14,534
Hi Guys,

I just complicated my database and I wanted to know what is the best practice for staff to access the APP. I have split my DB in 2. The back end stores the data and the front end is the App. The database will be placed on a network drive. In my DB I have 4 different forms, there are 4 different staff using the DB. Each have different task to do which is why I had to create different forms. The best way I thought for distributing the app is copy the App to the staff desktop and then go into Tools Ė Startup. I was going to select the form they need and of course uncheck certain boxes to make sure they canít access anything else.

I canít think of any other way to distribute the App. If anyone has any other suggestions please let me know. Thank you for all input.
Creating four different frontends is a viable option here particularly if you haven't imposed access levels to the users. Have you a user login which could determine the appropriate form for each user? You should also create a mde of the frontend to stop the user from altering the structure but backup the mdb file first.

Mary
Mar 13 '07 #2

P: 24
Hi Mary,

Thank you for your input. I did not think of setting up user login, which would probably be the easiest. Thank you for the advice.
Mar 13 '07 #3

MMcCarthy
Expert Mod 10K+
P: 14,534
Hi Mary,

Thank you for your input. I did not think of setting up user login, which would probably be the easiest. Thank you for the advice.
No problem.

Glad I could help.

Mary
Mar 13 '07 #4

NeoPa
Expert Mod 15k+
P: 31,494
Personally I'd store the front end (MDE if you like) on the network too, but create a form which starts automatically, which is programmed to switch to one of the other forms depending on the Network Logon Name of the operator. These could even be stored in a table for later flexibility. This would have the benefit of a single release if changes are required rather than trying to maintain four separate versions.
Mar 13 '07 #5

Post your reply

Sign in to post your reply or Sign up for a free account.