S
Shanin
I created an employee database back before we purchased a new timekeeping
system. Our old system has a 4 digit pin so I created our database to use
the pin as the employee number. In the new timekeeping system, the main
identifier is a 00-Name field, although they have the same pin for clocking
in and out that is linked to that. I find it somewhat crazy for us to have
to enter duplicative information in two databases. I can use a ODBC
connection to pull the information from FoxPro, and currently do for
schedules. I would like to just link all the information together so it only
needs to be entered into the timekeeping system and the employee database
just link to it. The problem is of course they currently have different
primary keys which I a few options on how to address. The point of my
question is would it be better to have it just linked, or have my database
actually run a query on open of the FoxPro table and then update the table on
in my employee database? The only reason I ask is because the employee
database is used to retain a history of past employees where as the
timekeeping one may be purged from time to time to reduce the size as well as
when an employee quits in the timekeeping system, the pin that currently
links to my database is deleted so it can be reused. The main data that I
would want to link would just be the address, phone number, etc,
system. Our old system has a 4 digit pin so I created our database to use
the pin as the employee number. In the new timekeeping system, the main
identifier is a 00-Name field, although they have the same pin for clocking
in and out that is linked to that. I find it somewhat crazy for us to have
to enter duplicative information in two databases. I can use a ODBC
connection to pull the information from FoxPro, and currently do for
schedules. I would like to just link all the information together so it only
needs to be entered into the timekeeping system and the employee database
just link to it. The problem is of course they currently have different
primary keys which I a few options on how to address. The point of my
question is would it be better to have it just linked, or have my database
actually run a query on open of the FoxPro table and then update the table on
in my employee database? The only reason I ask is because the employee
database is used to retain a history of past employees where as the
timekeeping one may be purged from time to time to reduce the size as well as
when an employee quits in the timekeeping system, the pin that currently
links to my database is deleted so it can be reused. The main data that I
would want to link would just be the address, phone number, etc,