Still a field with #Name? though every control has been renamed

L

Lars Gustavsson

I think I found it. It works anyway.

The problem was that I develop the application with an english version
of Access 97 under Windows 2000, and the problem occurs on a swedish
runtime edition of Access 97 on a Windows NT server. I've been told
that the problem could be with the Date() function, which is used.
When changing to Now(), it works as expected.

It's still strange though, how this could happend in the first place,
since the Date() function has been there for years, before I added a
few fields to the linked database table.

Thanks, for all effort to help!
 
J

John Vinson

It's still strange though, how this could happend in the first place,
since the Date() function has been there for years, before I added a
few fields to the linked database table.
Click to expand...

This appears to be the very common References bug. You can reset
References in a .mdb file, but not in a runtime. If ANY reference is
missing or misplaced (i.e. the .dll file is not found where Access
expects it), you'll get strange effects like this; in fact it's often
the case that Now() works but Date() does not.

Installing some completely unrelated software can break Access
references. It's a pain!

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps
 
Top