Access 2002 DATE() functions produces intermittent errors on repor

K

karen777

I have several applications with the same coding and no problems. This one
application intermittently loses it's mind. I have reports that I want the
date to appear on so that the date the user runs the report is reflected.
It's always worked in the past, but now when I go to run any of the reports I
get a message box that says "Enter Parameter Value" DATE. If I press OK,
the report opens and the date at the bottom of the report reflects #NAME!.
If I press CANCEL the report won't run. I have run into this last year
sometime and can't remember what the fix was. Do I have out-of-date Access
2002 (v10......). Do I need a specific library reference. Do I need a patch
to download. All my other apps work fine, as did this one for the past few
months. Now it has lost it's mind. Any ideas???? Thanks, Karen
 
J

Jeff Boyce

Karen

Have you checked the references? Is there a chance one/more of them is
marked "MISSING"?
 
K

karen777

Hi Jeff -

You are right on the money. A member of utteraccess.com instructed me to
try adding the reference "Microsoft DAO 3.6 Object Library" and it took care
of the problem. I am absolutely clueless on references. Do you have any
suggestions on where I could look to gain at least a beginner understanding?

Thanks for your help! Karen
 
F

fredg

Hi Jeff -

You are right on the money. A member of utteraccess.com instructed me to
try adding the reference "Microsoft DAO 3.6 Object Library" and it took care
of the problem. I am absolutely clueless on references. Do you have any
suggestions on where I could look to gain at least a beginner understanding?

Thanks for your help! Karen
Click to expand...


See Microsoft KnowledgeBase articles:
283115 'ACC2002: References That You Must Set When You Work with
Microsoft Access'
Or for Access 97:
175484 'References to Set When Working With Microsoft Access' for
the correct ones needed,
and
160870 'VBA Functions Break in Database with Missing References' for
how to reset a missing one.

For even more information, see
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html
 
Top