Mike,
If by PartNumber, you mean the Find PartNo Combo, that's because it's an unbound field,
so whatever happens to be entered displays on each record, until you change it. This
should not be a problem, but... you could always just null out the The PartNo after
"finding" the correct record.
Re ComboPopulatesMultipleFields, those values only "display" as a help to the user.
In your field list below, I'll assume that ProductID is the key field. If customers
order a ProductID, all you really need to save in the Order table would be the ProductID.
In any subsequent form, query, or report you would use that ProductID to rerelate it to
all it's ancillary information(CatrgoryID SupplierID, etc.. etc..)
Using the method in ComboPopulatesMultipleFields, you might want to "display only" the
ProductName and Description as an aid to the user, but not all the others. All that data
is stored in the original Parts table, and does not need to be captured every time someone
orders that Part.
--
hth
Al Campagna . Candia Computer Consulting . Candia, NH USA
Microsoft Access MVP
http://home.comcast.net/~cccsolutions
"Find a job that you love, and you'll never work a day in your life."