If it is a data entry form, it is best to use a *single table* as the form's recordsource, so you won't run into any conflicts with other tables while you are doing data entry.  If the form needs to bring in data from another table, use DLookup(), combo boxes, or other methods.  Queries are best for displaying data, such as in reports, or forms made for displaying data.

David, this is important advice. I think the role of queries as data source for Forms is important and a matter that constantly challenges new Access database developers. There IS a role for this sort of comprehensive data usage. Learning in which situations "DLookup" is the better way to fetch related table data may seem a point of lesser confusion for a seasoned developer whose experience guides the best practices, but it seems the rest of us need a lot of trial and error to entirely bring to heel.

Thanks, I was not aware of DLookup function. That could solve a few of my issues.

From my own experience, Dave. DLOOKUP is like having a query without having to have a query. However, Rick has advised me that it can slow performance when overused; and it may make life difficult when used at all on Forms meant to gather data. I have relied on CLZ TechHelp vids and the lessons offered here to perfect my understanding of their ideal usage. Imitating their role from well-built Forms is always best.