Tracking

[Victoria]

I have a database with one table with 25 fields that
stores information from auto titles. I now need it to keep
track of the employees who pass it on for a different job
duty. I have to create a way for users to enter who has
the title currently but also keep the history of who has
handled it. It may change hands 10 times. Can someone
please help?

Victoria

 

[Armen Stein]

I have a database with one table with 25 fields that
stores information from auto titles. I now need it to keep
track of the employees who pass it on for a different job
duty. I have to create a way for users to enter who has
the title currently but also keep the history of who has
handled it. It may change hands 10 times. Can someone
please help?

Victoria

Hi Victoria,

You can create a TitleTransaction (or TitleEvent, or TitleAction, or
whatever seems right) table to store these.

It will have a field that links to the primary key of the Title table,
say TitleKey. This relationship will be a "one-to-many" relationship
between the two tables in the Relationship window.

It should also have its own Primary key of an AutoNumber.

With this structure, you can store as many TitleTransactions as you like
for each Title record. Each one goes in its own record, and each one
can have a date, employee ID, transaction type, etc. To display and
enter these, use a continuous subform on a Title form.

Whenever you think about keeping track of a number of things in a
database, remember:

Good database designers know only 3 numbers: zero, one and many.

Multiple items should be in multiple rows, not in multiple fields.

Hope this helps,