Possible Reference issue related to RunTime?

[WSF]

Access97

I have several users in our company using an Access front-end mde on a
mix of W2K Pro and XPP OS's. Most work fine.
Only on a couple of the PC's I am striking the dreaded "Error Message:
Function Isn't Available in Expressions in Query Expression" issue where
a query fails and date-related fields in some forms end up with #Name etc.

To try to identify the issue I have run the Master MDB file on the
problem PC's but still have the problem.

I have been through the process of checking references as the likely
culprit. I have ensured the reference files and paths in the master MDB
file are replicated on the other PC's. The errors persist.

One thing I am not sure about is dll registration. If I merely overwrite
a dll file of the same name (with a later version of the file) does that
"new" file need to be re-registered in the registry, and if so how?
Can it be done within VBA in response to a trappable error?

The only difference I can now see in the mix of PC's is that the problem
ones are running Access Runtime (97), rather than the full Access
program. Could this be contributing to the problems?
I have not yet tried a full install of Access.

TIA

WSF

 

[Douglas J. Steele]

Overwriting the files generally isn't sufficient: you almost always need to
register them. You can use regsvr32.exe: see
http://www.granite.ab.ca/access/accesstovb.htm for details.

What references are you using? Are they all necessary? Remember that ANY
broken reference can affect functionality in other areas. Sometimes
developers forget to remove unused references, and they can lead to this
problem as well.

 

[WSF]

Hello Doug,
Thank you for your reply.

I am using
Visual Basic for Applications - vba332.dll Version 3.0.0.7019
Microsoft Access 8.0 Object Library - MSACC8.olb Version 8.0.0.3512
Microsoft DAO 3.51 Object Library - DAO350.olb Version 3.51.1027.0
Microsoft Excel 8.0 Object Library - excel8.olb Version 8.0.1.4307

I did actually copy what appeared to be later versions from my PC to the
problem PC, but did not re-register them. I will do so try again.

Cheers,
Bill

 

[Douglas J. Steele]

You can't legally copy the Excel Object Library. If the problem is that not
all of your users have the same version of Excel, then consider using Late
Binding instead so that you don't need a reference. Tony Toews has an
introduction to the topic at http://www.granite.ab.ca/access/latebinding.htm

And I just noticed that I gave you a wrong reference with respect to
regsvr32 before: obviously my copy to the clipboard didn't work properly!
The information about regsvr32.exe can be found at
http://support.microsoft.com/?kbid=161983