Date() fails in runtime with #name? URGENT PLS

gew:  Welcome to EE.

This doesn't sound like it is just the date() failing.  Do you get other weird errors - for example string handling, Mid$, Left$, etc.

It sounds like you either are missing a reference or you are having a conflict with Office 2000 and Access 97.  The reference problem is usually the VBA library.

Office 2000 will install over Office 97 unless you tell it other wise.  When this happens, it really screws up running Access 97.  If this is the situation, then you have to uninstall Office 97, rename MSAccess.EXE to something else and rename hatten.ttf to something else.  The reinstall Office 97 to another directory other than the default.  Go back and change the name back for the 2000 MSAcsess.exe

Jim

These is the notes I have in my electronic library that I got from Microsoft:

Remove the installation of Access 97, and then re-install it to a folder other than the default folder. To do so, follow these steps.

NOTE: Because there are several versions of Windows, the following steps may be different on your computer. If they are, please consult your product documentation to complete these steps.

Click Start, point to Settings, and then click Control Panel.

In Control Panel, double-click Add/Remove Programs.

Select Microsoft Access 97 or Microsoft Office 97 Professional from the list of products and click Add/Remove.

In the Maintenance Mode dialog box, click Remove All to remove Access 97.

Search you hard disk for a file named hatten.ttf and rename it to hatten.old if found.

Rename MSAccess.exe to MSAccess.old. The MSAccess.exe file should be located in C:\Program Files\Microsoft Office\Office.

Install Access 97 to a new folder, for example, C:\Program Files\Microsoft Office\Access 97.

Installations from the Office 97 Professional Compact Disc Only: Depending on the options that you select during a Custom installation, you may receive the following error during the reinstallation process:
Bdrintl.dll was unable to register itself in the system registry.
If this happens, quit the Setup program and do the following:

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

On the Start menu, click Run.

Type Regedit and click OK.

In the Registry Editor, delete the following key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\MSO97.dll
Close the Registry Editor.

Run the Office 97 Setup program again.

For additional information about the Bdrintl.dll error during setup, please see the following article in the Microsoft Knowledge Base:
Q162295 OFF97: Err Msg: "Bdrintl.dll Was Unable to Register Itself"
Rename MSAccess.old to MSAccess.exe.

BTW, you can get another 125 points by filling in a new member survey.  See Extra Points.

Guy:

I know that we have been talking about this situation via email and that you are going to be out until February.  However, there is an AutoDelete feature in EE which will delete this question within 30 days so it will be deleted by that time.

What do you want to do about it?

Jim

JimM,

We need to talk.   You are so angry at "Experts" who post half-baked Answers that you don't want to follow your own advice and post an Answer to this Q.

LOCK IT!  If qwe doesn't decide to award you the points, then he can reject the Answer and go from there, but there is no reason not to.

Mac

Jim, It's a payroll db with one directory (and .mdb) per company. The controlling .mde can only access one company at a time. So this is the uniqueness; it is only intended to be multi-user in that several payroll (ie for different companies) can be done simultaneously. Little data is entered, most is generated by the program as a record.

I'll have to call this q closed for the moment, even though another programmer checked the ODE setup machine and it is completely up to date. Hmmm. The answer to this will be satisfying! Guess I will reopen this in Feb by adding another comment or posting another q, not sure which.

Jim, posting this as opposed to emailing you because I'm interested as to whether you'll be notified since this q has been answered.

I think we have an accidental solution but no explanation. The user had never run Access 2000. The first time they did, it did some first time install stuff. Then they opened our ODE runtime app and lo and behold the #name? problem was gone.

The q is ... what did Access 2000 do on first use?

Don't worry about answering as I will post a new q if I can't figure it out or it doesn't prove generally applicable. Thought you might be interested.

Regards Guy

The first time Access 2000 is used, it sets up it's own Workgroup Admistration.  From that point on, until you switch back to Access 97, which I do regularly, the correct workgroup is set.  I don't believe that I realized this at the time and perhaps there should be a way to define this.

I'm not sure why the 97 ODE doesn't find the right workgroup.  As long as it works that is the key.

Jim