Link Data From Different Databases

[Guest]

I have a database that has personnel info in it - Table Name Is "T-Personnel
Data"

Now I need to create another data base for Training Records and would like
to capture certain Fields from my personnel Info Data base such as

Name - Rank - Serial Number

How can I do this so that when new records are added to the Personnel Info
data base they get added to my Training Database

Thanks - George

 

[John Vinson]

I have a database that has personnel info in it - Table Name Is "T-Personnel
Data"

Now I need to create another data base for Training Records and would like
to capture certain Fields from my personnel Info Data base such as

Name - Rank - Serial Number

How can I do this so that when new records are added to the Personnel Info
data base they get added to my Training Database

Thanks - George

Do you want a separate *DATABASE* - a separate .mdb file containing
multiple tables, forms, reports, etc.? or do you want a separate
*table* in your existing .mdb file? Unless there are strong reasons
otherwise I'd suggest the latter.

I'd also suggest - in EITHER case - that you should NOT store the
name, rank, and serial number redundantly in your training table.
You're using a relational database - use it relationally! Store the
personnel information ONCE, and once only, in [T-Personnel Data];
store training data, including the unique PersonID of the person being
trained, in the Training table, as a link. When you need to see the
person's name in conjunction with their training information, you can
use a Query joining the two tables, a Subform (showing the personnel
information on the mainform and the training data on the subform), or
a Combo Box (showing the person's name but storing the unique ID).

If you're using table datasheets for data viewing and entry... DON'T.
That's not their purpose and you'll find that they are of extremely
limited capability. Use the tools that Access provides: forms.

John W. Vinson[MVP]

 

[Guest]

John - This will be a totally separate database. I just don't want to keep
updating two different databases whenever we get a new guardsmen joining our
unit.

Thanks

I have a database that has personnel info in it - Table Name Is "T-Personnel
Data"

Now I need to create another data base for Training Records and would like
to capture certain Fields from my personnel Info Data base such as

Name - Rank - Serial Number

How can I do this so that when new records are added to the Personnel Info
data base they get added to my Training Database

Thanks - George

Do you want a separate *DATABASE* - a separate .mdb file containing
multiple tables, forms, reports, etc.? or do you want a separate
*table* in your existing .mdb file? Unless there are strong reasons
otherwise I'd suggest the latter.

I'd also suggest - in EITHER case - that you should NOT store the
name, rank, and serial number redundantly in your training table.
You're using a relational database - use it relationally! Store the
personnel information ONCE, and once only, in [T-Personnel Data];
store training data, including the unique PersonID of the person being
trained, in the Training table, as a link. When you need to see the
person's name in conjunction with their training information, you can
use a Query joining the two tables, a Subform (showing the personnel
information on the mainform and the training data on the subform), or
a Combo Box (showing the person's name but storing the unique ID).

If you're using table datasheets for data viewing and entry... DON'T.
That's not their purpose and you'll find that they are of extremely
limited capability. Use the tools that Access provides: forms.

John W. Vinson[MVP]

 

[John Vinson]

John - This will be a totally separate database. I just don't want to keep
updating two different databases whenever we get a new guardsmen joining our
unit.

Is there some way you can *link* from the Training database to the
personnel database, so that when you *do* update a person's name
(people do change their names, after all) or joins or leaves the
organization, that information is available?

If you're insisting on storing the same data redundantly in two
databases then you are creating the exact problem which you say you
wish to avoid.

John W. Vinson[MVP]