=Date() only works if I am logged on to Windows, why nobody else?

[Laftrip]

=Date() only works if I am logged on to Windows, why nobody else?

I have created a database and everything was going very well. Today I finished the database, and I was giving a presentation to some employees at work. When my boss opened my database on his laptop to test it, the very first form he opened has a text box that has a default value of =Date() and today's date wasn't there, instead it showed #name?. What a nightmare!

He told me not to worry, that the problem was probably his laptop. So we tried it on his PC. Same problem. Tried another PC at work, same problem.

So I started trying to figure out the problem, here is a resume of my discoveries.

- All PC's and Laptops are running Windows 2000 Professionnal
- Control Panel Regionnal Settings are the same
- Some have the same version of Access I was using, some don't (All have Access 2000, but different service packs is what I mean here)
- The database is sitting on a Mapped drive

Now here is the interesting part, on any PC where it doesn't work, if the user logs-off Windows and I log-in, IT WORKS!

If I create a new database, with a form, a textbox, default value = Date(), then it works fine for everybody.

So, here is the million dollar question: Why is there only a problem with that specific database for every Windows2000 user except me? I'm guessing it has something to do with my Windows Profile? But what? Why?

I've searched this forum, Microsoft Knowledge Base, other forums, Google, I can't find the answer. Is my database corrupted? Date() is a very basic Access function that gets the system time from Windows right?

Any suggestions anyone?

 

[Kodo]

this happend to me on a 2003 db. I installed SP3 on my box and the database gave #name? errors for some of the date fields. The only solution I found was to update the other workstations to the same patch level as my box.

 

[Laftrip]

My workstation is SP3, and so was at least one of the others I tried. But if somebody else logs on my "box", it doesn't work, and if I log on to their workstation (where it doesn't work for them), it works with my Windows log on.

I will double check, and consider applying patches, but I don't think this is the cause of my problem. I'm still 99% sure there is something in my Windows profile associated with this database, and I must seek-and-destroy this bug!

 

[Rich]

http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html