Error message in Access 2003

[jamshed_ver]

When I try to open my Database I get the following error message and the Date
Picker that I have in the database does not open. My OS is Windows XP SP3 and
I use Access 2003.

Your Database or Project contains a missing or broken reference to the file
‘mscomct2.ocx’ version 2.0.

The application you are attempting to use has a reference it cannot resolve
to an object, type library, DLL, or external database. Either the object,
type library, DLL, or database was deleted or its name has changed. Examine
the Available references list in the References dialog box in the Visual
Basic Editor (Tools menu) to determine if any action is required. If you did
not create this application, contact the programmer or administrator of the
system.
If the reference listed in the Available references list is preceded with
"MISSING:" clear the check box to remove the reference if it is no longer
required. If you still need to use the reference, clear the check box entry
for "MISSING: <referencename>" in the Available references list, and then
create a new reference to the file using the Browse... button. If this is an
installed database application, you may need to reinstall or repair the
application.

After following the instructions in the error message, by going to the
Available References, I found the following entry ticked.

MISSING: Microsoft Windows Common Controls-2.6.0(SP3)

Help appreciated.

 

[Tom Wickerath]

My OS is Windows XP SP3 and I use Access 2003.

Are you sure the SP3 is not for Access 2003? I don't believe there is a SP3
for Windows XP (at least not yet):

http://www.microsoft.com/windowsxp/downloads/updates/default.mspx

You can click on Start | Run and enter the command: winver
to verify the service pack of your Windows operating system.

After following the instructions in the error message, by going to the
Available References, I found the following entry ticked.

MISSING: Microsoft Windows Common Controls-2.6.0(SP3)

You most likely do not need this control, unless you are currently using the
ActiveX-control based method of opening a common dialog file. Try deselecting
this missing reference. Then click on the OK button to dismiss the References
dialog. To determine if you needed this reference, click on Debug | Compile
{ProjectName} while still in the Visual Basic Editor. You will know right
away if you have a compile error (which may be unrelated to this reference).
However, if your code compiles without squacking, then you did not need this
reference in the first place. A successful compile is evidenced by this menu
command appearing "greyed out" if you try to repeat it immediately after
compiling the first time (ie. no other changes in the code).

It is best to "starve" the references list; ie. only include a checked
library reference if it is required for your VBA code to compile correctly. I
often times find other's databases with a boatload of unnecessary references
checked. Not only does this consume RAM memory needlessly, since any checked
libraries are loaded into memory, but it also increases the chances of a
given person experiencing a MISSING reference error.

Here are two excellent articles on this topic:

Solving Problems with Library References (Allen Browne)
http://allenbrowne.com/ser-38.html

Access Reference Problems (Doug Steele)
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

If you find that you definately need this control, then you may want to
consider re-writing the code that is dependent upon it. However, it is not
unusual to find totally un-related compile errors that have gone
undiscovered, due to the default VBE (Visual Basic Editor) setting for
Compile On Demand.


Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________