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!

Design Issue...Need a little guidance...

Status
Not open for further replies.

Torn39

Technical User
Jul 25, 2002
14
US
I'm very new to "designing" Access applications and I was hoping one or more of you could give me a little guidance. I've come to the "fork in the road" in this project and I'm just hoping someone can point me in the most efficient direction I should take...

Here's the quick overview. I've got a main database that holds all the service orders I have to distribute. I've got a "management form" that can decide which laptop (5 possible) get which service orders for each day. This all works fine...

Now I have to get these service orders to the individual laptops, they work on them, then send them back to the main database. Using standard update and append functions shouldn't be that hard to get them back.

Since the "main form" for the laptops differs significantly both in form and functionality (ie - the manager, who assigns the orders, will use a different form than the workers, who just need to retrieve their worklists for the day, enter info on these records, then send it back to the main office), do I create a "new database" for the workers/laptops and just query the "main" database to get the individual laptop work orders for the day? Or should I just have the "main database" and use some sort of security permissions to allow/restrict access to different forms...

As I'm working on this using a couple doorstop books, the forum has been great.

Thanks for your help/suggestions...

Drew
 
I would suggest using different mdb's for the laptops...

One, these mdb's don't need security because the laptop goes with the user to the work site and all that god stuff....

two, why troble yourself with making one database do all of it, this way only the funcions that are needed are in each database...

third and last, i think it'll be easier on the users to know that what's there they can use... they don't have to worrie about menu items that don't work...

Just my thoughts...

--James junior1544@jmjpc.net
Life is change. To deny change is to deny life.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top