Date()
- Thread starter vish
- Start date
scottfarcus
Registered User.
- Local time
- Today, 06:41
- Joined
- Oct 15, 2001
- Messages
- 182
Go to any code module.
Click Tools>>References.
Uncheck Microsoft DAO ...
Close the references dialog.
Click Tools>>References.
Find and check Microsoft DAO ...
Click Tools>>References.
Uncheck Microsoft DAO ...
Close the references dialog.
Click Tools>>References.
Find and check Microsoft DAO ...
boblarson
Smeghead
- Local time
- Yesterday, 22:41
- Joined
- Jan 12, 2001
- Messages
- 32,040
Never heard of the DAO causing a problem in the Date() function. But I have plenty of experience with the Microsoft Common Controls (comctl32.ocx) being the culprit with this and the Mid, Left, and Right functions as well.
I would do the same thing about the references (Tools/References) and see if the Microsoft Common Controls is listed as MISSING. Even if it is not (as it will happen with it not listed as missing sometimes), I would uncheck the box, and then close the dialog. Then reopen, Tools/References and use the BROWSE button to go to the comctl32.ocx file and click on it and then hit ok until you close the reference dialog box.
Then, it's an 80% chance that your function will work (just have had that happen many times personally).
BL
hth
I would do the same thing about the references (Tools/References) and see if the Microsoft Common Controls is listed as MISSING. Even if it is not (as it will happen with it not listed as missing sometimes), I would uncheck the box, and then close the dialog. Then reopen, Tools/References and use the BROWSE button to go to the comctl32.ocx file and click on it and then hit ok until you close the reference dialog box.
Then, it's an 80% chance that your function will work (just have had that happen many times personally).
BL
hth
- Local time
- Today, 00:41
- Joined
- Feb 28, 2001
- Messages
- 30,566
When you upgrade from Ac97 to Ac2K, some of the libraries change and you need to upgrade the references. The advice given you earlier is absolutely accurate. Look in the Tools>>References dialog box to see whatever is missing. Browse for it. Re-establish the link to the file in question.
In some cases the problem is simply that a version number has changed. For me the culprit was DAO35.DLL became DAO36.DLL, all other things being equal.
And the Date() function is just the first function call you tripped over. But in fact, ANY function call would have provided the trip wire. The last time I saw this, it was the Left$ function that got me. But it was some other library that was actually missing. Access is kind of dumb about this sort of thing, so it points to the wrong problem sometimes - like right now.
[This message has been edited by The_Doc_Man (edited 06-06-2002).]
In some cases the problem is simply that a version number has changed. For me the culprit was DAO35.DLL became DAO36.DLL, all other things being equal.
And the Date() function is just the first function call you tripped over. But in fact, ANY function call would have provided the trip wire. The last time I saw this, it was the Left$ function that got me. But it was some other library that was actually missing. Access is kind of dumb about this sort of thing, so it points to the wrong problem sometimes - like right now.
[This message has been edited by The_Doc_Man (edited 06-06-2002).]
scottfarcus
Registered User.
- Local time
- Today, 06:41
- Joined
- Oct 15, 2001
- Messages
- 182
It may not appear as MISSING:. I've had trouble with DAO with Date() and Format() and, after checking my references, it did not list ANY as MISSING:. However, when I re-established the link to DAO, all was well.
Sorry I couldn't help.
Sorry I couldn't help.
Similar threads
