G
Guest
I have a large pre-existing database full of equipment holding lots of
information about each piece. While I need to account for each piece by
model number, serial number and location, I also need to keep track of
certain info on just the model number of each piece of equipment. Placing
the Master table in a query and changing the “show unique†property to yes,
my list reduces from 4500 pieces down to 800 unique pieces of equipment.
I am lost from staring too long at it. I am trying to split the database
into one-to-many relationships defining which model number parts are where
and how many of each are in different departments. What am I missing? Can
anyone offer an idea or a resource to read? Maybe I should be trying to work
more with a query rather than splitting the large table?
As always thank you.
information about each piece. While I need to account for each piece by
model number, serial number and location, I also need to keep track of
certain info on just the model number of each piece of equipment. Placing
the Master table in a query and changing the “show unique†property to yes,
my list reduces from 4500 pieces down to 800 unique pieces of equipment.
I am lost from staring too long at it. I am trying to split the database
into one-to-many relationships defining which model number parts are where
and how many of each are in different departments. What am I missing? Can
anyone offer an idea or a resource to read? Maybe I should be trying to work
more with a query rather than splitting the large table?
As always thank you.