>>You still have one more option. You can bring up just one table (master) and provide custom controlsource (method seeking in lookup) for all columns showing lookup fields. Surely, this columns will become read-only, but usually it's Ok.
>
>The thing I'm worried about now is not really a lookup situation. (Though I'm sure I'll need that, too) My problem is that I have a grid that lists all trips for the day. Because of normalizing, the client name is not attached to the trips. So the user has no way of seeing who the trips belong to. So I need to include the name from the clients table, and the rest of the info from the trips table, with the common key being clientID.
>
>The way I understood the instructer to be saying to do it is to have the customer table and the trips table open with a relation, then in the grid have clients.name and trips.(whatever) for control sources.
>
>So you're saying to do that with a view? What happens if I append a record to the view? Does that append a record to the trips table? Or do I need to write special code to tell it what table to append to?
>
>Thanks,

It's either view or, as I said, trips table is master, and customer table is lookup. View supports all appendings, deletions etc, and send data changes back to table. Another way will support it too. However, some programming will be needed in both cases, simple and doable.