Default Value

Thanks, Kevin. That didn't quite address what I am trying to do, but perhaps I need to bite the bullet and get access to the extended cut. Appreciate your help.

I should have given your answer more credit. Expert 9 discusses the very topic. Working on it now. Thanks again.

You also need to ask yourself if you need to have that information duplicated on the second form because if you can look up that value from the customer table, then there's no reason to copy it over to the second form. The only time you ever want to do that is if you care about historical data, for example, you can copy over an address to an order if you care where that address was shipped. At some point in the future, if the customer changes their address, then it won't change on all of their orders. But for something like their name and customer number, if you can look that up from their customer ID, sometimes that's better.

Hi Richard, thanks for your reply! I have several orders I may be working on during the course of the day and I am opening forms from the order form (and from other forms) and if I return to a shipping form, for example, and it doesn't display the order info, or the customer info, I won't know if I opened that shipping form for the order I have open now, or if it opened for an order I was looking at an hour ago. So, I want something displayed to quickly identify that situation for me. The customer name is a perfect tool to do that. By the way, Kevin's hint at default value is working fabulously! Thanks again for the nudge in the right direction.

Yeah, using the default value is a great way to pull that information into the new form, but if you only need to display it, you might be better off with an unbound field and a DLookup. You're not duplicating information in multiple tables that way then.

I'm gonna make a video on this one. Stay tuned.