Manage forms, Queries and Reports in one Database, Tables in another

[Deborah Najm]

Hello,

We have an in-house application that we are currently using several copies
of, one database for each client.

I was wondering if there was a way keep all the queries, forms, reports and
modules in one database, then have a method in that database to choose which
tableset database I would want. I would then have a database for each
client with only the tables.

Deborah

 

[Guest]

I'm not real clear on what you are trying to do, but it sounds like you might
want to look into splitting your database. By splitting the db, you would
have a backend and a frontend. The backend contains only the tables and
would be placed on a network share where everyone with the frontend has
access to. The frontend contains only the forms, reports, queries, modules,
etc. and is linked to the backend's tables.

HTH,
Al

 

[Deborah Najm]

Would you be able to link to multiple backends with one frontend?

 

[Guest]

Yes, in fact, you can try it out by opening any database to the local tables,
click on "File", "Get external data", and "Link tables". Then browse to any
database (even an ODBC connected database - by changing the "Files of Type"
to "ODBC Databases" at the bottom of the browse window), select the database,
and then select the tables you want to link. You disconnect the link simply
by deleting the link from the sharing database and the parent database's
table is unaffected. (just make sure you are deleting the linked table and
not the parent table) The linked tables are easy to identify by a little
arrow next to the table name.

To take it one step further and split the database into a frontend and
backend, use the Split Database wizard under "Tools", "Database Utilities",
"Database Splitter". This is a good way to have everyone accessing and
updating shared tables; otherwise, you have multiple instances of the
database on your users machines without sharing their updates and additions.

HTH,
Al