Date function misbehaving

[flutegirl]

Howdy.

I lurk here frequently, but this is my first post.

One of the users of my Access database is having an interesting problem this morning. For some reason, she is suddenly unable to run any forms on which I've used the Date function (to return current date), either as the default value for a field on the form, or in code on the form's class module. She gets a compile error, as if the library was missing. This was the first thing that I checked, and it's not missing...alas. This database is shared over the network (not replicated or split at this point--all users are using the same copy of the dbase), and she is the ONLY user with this problem.

Things I have checked:
1. The problem occurs consistently throughout all forms/tables--it does appear to be a problem with the function itself, not the surrounding code on one form.
2. The reference for "Visual Basic for Applications" IS selected.
3. vba332.dll is in the right place on her machine, and the same size as the file is on my machine. I have pondered that the file could be corrupt on her machine, but I have not tried replacing hers with mine yet.
4. Banging my head against the desk. Surprisingly, this didn't help.

Has anyone ever run into this before?

Thanks,
Marcia

 

[jofarrell]

Check and see if her local time settings on her computer have changed. The date that the program is exepcting could be long as opposed to short form, or vice versa. I experinced an error similar to this and that was the cause. You can actually bypass regional settings in your coding but for now you may just want to see if they are all using the same date format where it doesnt sound like a program issue.


Hope that helped some.

Joanne