Date function error

  • Thread starter Thread starter andrew3254
  • Start date Start date
A

andrew3254

Hello,

I have a field on a form called "Date Submitted" it is an auto generated
field which uses the Date() function.

It works on my machine but no one elses. The only difference is I have
upgraded to Office 2007 and everyone else is still using Office 2003. The
format of the database hasnt changed, it is still 2000. It was working
before but I changed a couple of other fields (not the one im having problems
with) and it now doesnt work for everyone else.

Anyone have any ideas?
 
The problem seems to be that Access cannot find the function Date(), I have
changed the function to Now() and it works fine but is there a way of fixing
Date() to save me having to go through and change all the instances of Date()
 
andrew3254 said:
The problem seems to be that Access cannot find the function Date(), I
have
changed the function to Now() and it works fine but is there a way of
fixing
Date() to save me having to go through and change all the instances of
Date()
Click to expand...

You might have some object(s) named "Date". Worth a look.

Keith.
 
Odds are it's a problem with the References collection, caused by the fact
that your workstation has different versions of the libraries than the
workstation on which the database was created.

You need to go into the VB Editor and get into the References dialog (sorry,
I don't have Access 2007 installed on this machine, so I can't give you
detailed instructions for how to do that). Once you're there, examine all of
the selected references (the checked ones at the top of the list). If any of
them have "MISSING:" in front of them, unselect them and back out of the
dialog (make sure you write down what references you delete, since they'll
be in a different order when you go back in...). Go back in, find the
reference(s) you just deleted and add it/them back.

If none have MISSING: in front of them, select an additional reference at
random, back out of the dialog, then go back in and unselect the reference
you just added. If that still doesn't solve the problem, go back in,
undelete as many of the selected references as you can (Access may not let
you unselect them all), back out, then go back in and reselect the
references you just unselected.

I'm assuming that the application is split into a front-end (containing the
queries, forms, reports, macros and modules), linked to a back-end
(containing the tables and relations) as it should be, so that you'd be
working on your own personal copy of the front-end. If not, have that done
before you do that above, or you'll prevent all other users from being able
to work with the application.
 
Thanks Doug,

Found the problem before reading your reply, the problem was a clash of the
different Outlook references all works fine now.

Yes the database is split into a front and back end. I am just deploying a
new front end.
 
You may want to look into using Late Binding so that problems like that
don't occur again.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


andrew3254 said:
Thanks Doug,

Found the problem before reading your reply, the problem was a clash of
the
different Outlook references all works fine now.

Yes the database is split into a front and back end. I am just deploying
a
new front end.
Click to expand...
 
Back
Top