Access database

  • Thread starter Thread starter Gary
  • Start date Start date
G

Gary

I have a main database then I created 7 databases with
limited information for different departments in them. I
can't get the new databases to import the information
from the origianl database. The fields remain blank. I
have linked the tables together and have had no luck so
far. Anyone have some ideas or suggestions.

Also another issue is I have some calculated fields in
some forms but those calculated fields show up balnk in
the main database. Anyway to fix that?
 
I have a main database then I created 7 databases with
limited information for different departments in them. I
can't get the new databases to import the information
from the origianl database. The fields remain blank. I
have linked the tables together and have had no luck so
far. Anyone have some ideas or suggestions.

Also another issue is I have some calculated fields in
some forms but those calculated fields show up balnk in
the main database. Anyway to fix that?
Click to expand...

Did you create seven *databases* - .mdb files, containers for multiple
tables, forms, reports, etc.? Or seven *tables* within your database?

How are you trying to "import"?

Linking tables does not (and should not!) copy data from one table to
another; storing data redundantly is never a good idea. If your seven
databases/tables contain similar kinds of data, and have the same
field structure, a better design might be to add a Department field
and store all the data in one table; a Query can select the records
for a particular department.

Calculated fields SHOULD NOT be stored in tables, period.
Storing derived data such as this in your table accomplishes
three things: it wastes disk space; it wastes time (almost
any calculation will be MUCH faster than a disk fetch); and
most importantly, it risks data corruption. If one of the
underlying fields is subsequently edited, you will have data
in your table WHICH IS WRONG, and no automatic way to detect
that fact.

Just redo the calculation whenever you need it, either as a
calculated field in a Query or just as you're now doing it -
in the control source of a Form or a Report textbox.
 
-----Original Message-----


Did you create seven *databases* - .mdb files, containers for multiple
tables, forms, reports, etc.? Or seven *tables* within your database?

How are you trying to "import"?

Linking tables does not (and should not!) copy data from one table to
another; storing data redundantly is never a good idea. If your seven
databases/tables contain similar kinds of data, and have the same
field structure, a better design might be to add a Department field
and store all the data in one table; a Query can select the records
for a particular department.

Calculated fields SHOULD NOT be stored in tables, period.
Storing derived data such as this in your table accomplishes
three things: it wastes disk space; it wastes time (almost
any calculation will be MUCH faster than a disk fetch); and
most importantly, it risks data corruption. If one of the
underlying fields is subsequently edited, you will have data
in your table WHICH IS WRONG, and no automatic way to detect
that fact.

Just redo the calculation whenever you need it, either as a
calculated field in a Query or just as you're now doing it -
in the control source of a Form or a Report textbox.



.
Click to expand...

Thanks John,

I ended up just letting it auto calc in the reports
and left them out of the database. Thanks for the info.
 
Back
Top