If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
many databases, one project
Hi,
I am about to embark on an Access project for my company. They are interested in several different databases. Special Orders, Discontinued Products, Demos etc. These databases are unrelated. What is the way to go about this? I have no problem creating separate databases for each application. Or do I create one big database? And if I do create one database, how would I keep track of which tables, forms, queries etc belong to which? And if I create separate databases, how do I put them all together so the user thinks it is just one application? Thank-you, Liane -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200902/1 |
#2
|
|||
|
|||
many databases, one project
On Fri, 13 Feb 2009 03:14:45 GMT, "timbits35 via AccessMonster.com"
u34694@uwe wrote: I am assuming Special Orders are orders of certain products. Discontinued Products are products with a Status attribute set to Discontinued. Demos are for certain products. Special Orders are placed by some customers. Demos are given to some customers (perhaps with Status="Prospect") As you can see these three subjects are very much related. So I'm thinking ONE back-end database with all tables. How many front-ends (FE) does not matter as much. You can have one FE with a main ribbon to choose the Special Orders section, Disc.Products section etc. If you are unclear about the db and application design you should consult with an expert before you make some rookie mistakes that will haunt you for a long time. "Microsoft Solution Provider" in your yellow pages is a good place to start. -Tom. Microsoft Access MVP Hi, I am about to embark on an Access project for my company. They are interested in several different databases. Special Orders, Discontinued Products, Demos etc. These databases are unrelated. What is the way to go about this? I have no problem creating separate databases for each application. Or do I create one big database? And if I do create one database, how would I keep track of which tables, forms, queries etc belong to which? And if I create separate databases, how do I put them all together so the user thinks it is just one application? Thank-you, Liane |
Thread Tools | |
Display Modes | |
|
|