View Single Post
  #3  
Old December 18th, 2006, 08:01 PM posted to microsoft.public.access.forms
John Vinson
external usenet poster
 
Posts: 4,033
Default Autopopulate Problem, i.e., Null Value

On Mon, 18 Dec 2006 10:16:00 -0800, rszebras
wrote:

Please ignore my prior post. I figured out why I was getting the null value
problem. It's because the table associated with the form says that the field
is required. But that raises another problem.

The table that the form populates must have the client's name, address,
phone number, etc., stored there.


I think you're mistaken. It is almost NEVER necessary to copy data
redundantly from one table into another table. If you're assuming that
you must have all the information in one table in order to use it,
that assumption is simply wrong.

You're using a relational database. USE IT RELATIONALLY! Store the
name, address, etc. *once*, and only once, in the Client table where
it belongs. If you need that information in conjunction with data in
some other table, say for a Report, store the ClientID and use a Query
joining the Client table to this other table; base your Report *on
that query*, choosing your table's fields from your table, and the
client information fields from the client table.

John W. Vinson[MVP]