"Bryan Warren" wrote
yes i now it does not follow DB
normalization. but that is not my
goal. however it is needed for
inventory purposes. thanks for
the info.
Normalization is not a "goal". It is just following good design practices,
and will, sooner or later, save you time, effort, and frustration.
I am intrigued by your response: If the data is there in one Field, why
would it be necessary to have duplicate data in another Field "for inventory
purposes"? Why not just use the "ID" Field wherever you'd otherwise use the
"Computer Name" Field?
Help me understand, because it does not make sense to me that there can be a
_need_ for two Fields in the same Record to contain identical information.
If there are circumstances when it is meaningful for them to contain
different information, that would be another thing altogether.
Larry Linson
Microsoft Access MVP