Actually I wouldn't do what mmcdonal suggests.
"Null" is NOT the same as Null. Why put values in your table if you don't have data for them?
I would suggest that you check your table constraints to see if the fields that you are not entering require a value. If so, then you should put edits on the form to force entry.
I do see where mmcdonal's solution would work.
If you are building the SQL string based on the field values using something like:
sql = sql & "Field1 = " & me.field1
This will make a "valid" SQL statement where you didn't have one without change the value of the field to "Null".
However, if you're using
sql = sql & "Field1 = """ & me.field1 & """"
as you should be doing to make sure you build a valid SQL string if the value of me.field1 has a space in it, your table will store the word "Null" if the field is not entered on the form.
In short, since you're building the SQL statement yourself, make sure it has valid SQL syntax.
Randall J Weers
Membership Vice President
Pacific NorthWest Access Developers Group
P.S. Actually, on further review I notice that I would do what mmcdonal suggests. But there is a way that doesn't require using an extra variable which I describe in a later post. Also, mmcdonal's way doesn't cover building a valid SQL if your field has a space or special character in it. Sorry mmcdonal.