In some of my forms and code, I am using the =Date() function. However, on some computers, this function does not work. Why would it work on some computers and not the others?
This just a shot in the dark. Try, on one of the computers where the Date Function isn't working, open the Visual Basic Editor (Keys Alt-F11 together). From the Menu, select Tools-> References, if Microsoft DAO Object Library isn't ticked/checked, find it, tick/check it (the one with highest number), let me know if that solves the problem or not.
I'm having the same problem, more usually with the Format function. However, my problem always occurs on PCs with runtime licences for Access - I therefore can't get to the Tools | References menu on those PCs. Most other functions work, but these do not.
Further, this happens in queries as well, not just in VBA.
I'll be very interensted in any answers to this thread.
Hi hughesai, yours could be 1 of 2 problems or possibly both.
1. The original .mdb or .mde file wasn't properly referenced before being packaged. To resolve that, do as I've suggested above, re-package and re-deploy.
2. When the .mdb or .mde file is being packaged a necessary Library isn't being added. As I'm sure you know, this isn't an automatic procedure for all Libraries/Files, sometimes certain Libraries/Files have to be Scanned.
Without actually seeing the DB, I can't really suggest anything else.
In the first version of Access 2000 the Date() function will return the current date. In Access 2000 SR1 you have to use the Now() function to do this.
I have had problems with some PCs on my network treating date calculations differently to others, because some had SR1 and other hadn't.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.