Multiple Databases in one

[Anthonydb]

This may be a little long winded so please excuse me. I'm looking for the easiest way to create I guess what you could call multiple profiles for a database. In other words, I have one database but I want to have a situation where, when the splash screen appears, here are the choices: D.C., New York, Rockville, Disctricts

I need these to be seperate entities in one database. When any location is picked all of items pertaining to that site become applicable and only those for that site. I'm thinking that I have to copy all of the tables and make them site specific but, will I also have to do the same for the forms?

I know the other alternative is to create seperate databases but that is something I want to avoid. I think I have the idea for what has to happen but I want to be sure. I'm thinking that unless I do everything in VB code, which I'm not very good at, I will have to x number of forms and tables since the forms are tied to one table or query.

If I knew code well enough, I believe it would some process of elimination using unbound controls on the forms. For instance, something along the lines of: If startup = Rockville then....
else If startup = D.C. then
form = whatever

Any assistance in the matter would be greatly appreciated.
Thanks

 

[dcx693]

You can do this all in one single database, but it will involve some coding in the process. Trust me, you'll be much better off for it in the long run rather than trying to keep track of multiple separate copies of the database.

You can have the splashscreen come up just as you described. Once the user makes a choice of what area they want to work with, all the forms and objects can pick out the correct data to display. No need for separate tables or queries. The forms and report can all adjust themselves based on the user's initial choice.

 

[Chasedog]

Try using a switchboard. The main switchboard directs into a form with command buttons for all the functions of that choice, ie Rockville. When building your forms, reports, etc. base them on queries for each group. Then you can just copy the form/report and change the source.

 

[Anthonydb]

Was I in the right area with the code I was describing or would select case be more appropriate? Any good books you can recommend on the using of VB code with unbound controls and anything else I'll need to make this work?

Thanks again.

 

[dcx693]

The Northwind sample database that ships with Access might be a good starting place. I think I remember it having a switchboard-type opening form.

To answer your question, Select Case is a good construct to use when you have more than 2 choices, and your choices are fairly distinct. The If...Then structure gets confusing if you start having ElseIf statements in there.