Please clarify: do you have a one-to-many like:

Things: ThingID|ThingInfo|LocationID
Locations: LocationID|LocationNumber

or do you have a many-to-many, which looks like:

Things: ThingID|ThingInfo
Locations: LocationID|LocationNumber
Thing2locs: ThingId, LocationID

If it's the former, then you can use a comboBox for assigning the LocationID to the Thing. The row source could be a SQL-select (my preference) or Field source from a table... The combo box can bind the LocationID, but display the location # to make the user's life better.

>I have a thing table and a location table related many to many (some of you talked me into it) using a common child table, giving thinglocations. The location table didn't exist before. I had a form with controls for thing.fields and a grid for thinglocations, which was just a child. All that is in the location table is a key and a location number, which was in thinglocations. The grid still needs to show location numbers, but now they are not in the grid.recordsource. This old app was designed for standalone use and uses tables, not views. I just realized that I'm not even sure about the correct way to use views with a basic parent-child form that uses a grid. Thank you.