>I have a problem that may actually be very simple. I am trying to track the status of several items. they are all serialized. When I add a new serialized item I want to be able to automatically create a table for it by using the serial number of the gear that I load into the table that stores the actual configuration of the gear. I load all of the status data via a standard text file. It is not sufficient for this application to just create a view of the table as I need to be allow the user to select a particular serial number and transfer only that table to a different unit.
>

I am thinking any replies you get will question why you need a table for each item, starting with mine.

Do these tables have multiple records? If so, could this be handled as 2 tables - parent and child. The parent table could have general info about the item including SN. The child table could have the unit, and other historical specs [including history of unit assignment -- e.g., 1 record per unit assigned] on the item.

Otherwise, I think you are in for a nightmare trying to keep up with a growing number of tables that basically contain the same information.