Unregistered/Missing references

[Ron Carr]

I am getting all sorts of errors installing a database on
a client's system. Turns out Microsoft Common Controls
5.0 is flagged as Missing in references. It refers to
Windows/system321/comctl32.dll, which is in fact right
there. Is there a way I can properly register this, so it
is not "Missing"???

Thanks!

 

[Allen Browne]

Welcome to DLL Hell.

Try:
regsvr32 "C:\Windows/system32/comctl32.dll"

These common controls (and some ActiveX controls) are a nightmare for
registrations, installation, version upgrades, etc, etc. Best to avoid them
if at all possible, and use the API calls directly if possible.

Details:
http://www.mvps.org/access/api/index.html

 

[Ron Carr]

Thanks I will try this ASAP. Visited the site you gave me
and it is very helpful. However, the Common Controls set
seems indispensible and irreplaceable, as it contains all
(?) of the most common functions (trim, left, mid etc,).
Am I missing something?

 

[Allen Browne]

No, no. The common functions you referred to are part of the VBA library.

To verify that, open the Immediate window (Ctrl+G) and enter:
? VBA.Left(
You will see the Intellisense provide the functions as part of VBA.

Alternatively, press F2 from any code window to open the Object Browser and
see what is part of what library.

 

[Douglas J. Steele]

Thanks I will try this ASAP. Visited the site you gave me
and it is very helpful. However, the Common Controls set
seems indispensible and irreplaceable, as it contains all
(?) of the most common functions (trim, left, mid etc,).
Am I missing something?

As Allen says, those functions are in the VBA library, not the Common
Controls library. References are like apples: one bad one spoils the whole
bunch. When Access goes to find a function, if any reference is broken, it
impacts the ability to gets functions from references that are okay. You can
lessen the problem by always qualifying your usage (i.e.: use VBA.Trim
instead of just Trim)