Problem with date field

I have a database I've developed over the years using Access 2003.  The company I developed it for is still using 2003.  On a form in the database I have a text box with a default value of =Date().  When the form is launched with 2003 the field has today's date filled in which is exactly how I want it to work.  This form also works fine on my computer using Access 2010.  But now when I make an alteration to the Front end database which contains the form in question using my Access 2010 version and upload it to my customers computer system, which is still using 2003, the field gets populated with "#Name?" instead of today's date.  Why is this happening?

--Steve
SteveL13Asked:
Who is Participating?
 
Gustav BrockConnect With a Mentor CIOCommented:
Sounds like a reference is MISSING.
Look up menu Tools, References and sort out any MISSING reference.

/gustav
0
 
GRayLCommented:
Are you saying the Control Source property of the text box is:
=Date()

To set the Default property, do not use the equal sign.  Although A2003 text box will accept both =Date() and Date() as Default values, most probably A2010 will not.
0
 
SteveL13Author Commented:
It is not the control source.  It is an unbound field.  I've tried both =Date() and Date() and still have the same problem.
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
SteveL13Author Commented:
(In the default value)
0
 
Jeffrey CoachmanMIS LiasonCommented:
Set the Default value in the Table, not the Form...

This works fine for me in Acc2003/Acc2010
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
RE: "But now when I make an alteration to the Front end database which contains the form in question using my Access 2010 version and upload it to my customers computer system, which is still using 2003"

Steve ... are you saying that ... you are modifying the A2003 MDB in the A2010 environment, then uploading to back to an A2003 environment.  If so, there have been several reported issues with this scenario, even though in *theory* ... if you do *not* use any new features of A2010 on the MDB (which DO show in the property sheets - even though it's still an mdb) ... you can do this, it's apparently can be problematic.  However, as Gustav notes ... high probability of a Reference issue.

mx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.