New Linked Table

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My database is split but now I need to create a new table. do I create it in
the backend or in the mdb where the forms and such are? How do I do this?

steve
 
You create the new table in the BE. Kick everyone out of the database and
open the BE. Create the new table. Open up the Relationships window and
create the properly relationships between the new and existing tables. Close
the BE.

On the FE go to File, Get External Data, Link Tables. Add the newly created
table in the BE. Create or modifiy any queries, forms, and reports as
necessary. Test. Distribute the modified FE to the users.

But before doing all the above, ask yourself why you need a new table. Be
very certain that you do before messing with a working design.
 
I have the same probkem. I want to create a different table for each year.
Can it be done by checking te year of the curent date in VB Code?
The table has to be created in the BE but from the FE.

Thnx.
 
I have the same probkem. I want to create a different table for each year.
Can it be done by checking te year of the curent date in VB Code?
The table has to be created in the BE but from the FE.

Thnx.
 
Why? Having multiple tables for the same information is seldom (if ever) an
appropriate design.

Have a single table, and include a mechanism to determine the year.
 
Why? Having multiple tables for the same information is seldom (if ever) an
appropriate design.

Have a single table, and include a mechanism to determine the year.
 
in general, a bad idea. it breaks normalization rules - storing data in a
table name. it will require either creating a separate set of forms,
reports, etc, for each year, OR changing the table reference everywhere you
use it in the database, every single time you want to see data from a
different year.

much, much, much easier to keep all the data in the original table(s). you
can pull records for a specific year by simply setting criteria in a query,
or filtering forms and reports directly.

hth
 
in general, a bad idea. it breaks normalization rules - storing data in a
table name. it will require either creating a separate set of forms,
reports, etc, for each year, OR changing the table reference everywhere you
use it in the database, every single time you want to see data from a
different year.

much, much, much easier to keep all the data in the original table(s). you
can pull records for a specific year by simply setting criteria in a query,
or filtering forms and reports directly.

hth
 
Back
Top