zimmer9
asked on
How to resolve the error "Missing: Microsoft Common Dialog Control 6.0 (SP3) in VBA Reference for application written in Access 2003 and now I open it in Access 2010?
How to resolve the error "Missing: Microsoft Common Dialog Control 6.0 (SP3) in VBA Reference for an application written in Access 2003 and now I open it in Access 2010?
In addition, when I open the application in Access 2010, a message box appears:
Your Microsoft Access database or project contains a missing or broken reference to the file 'comdlg32.ocx' version 1.2.
In addition, when I open the application in Access 2010, a message box appears:
Your Microsoft Access database or project contains a missing or broken reference to the file 'comdlg32.ocx' version 1.2.
Are you using the Calendar Control ?
If so that has been replaced with the Data Picker available in any Text Box wherein the Control Source is a DataTime Data Type.
From that KB:
"This package is provided under the terms of the End User License Agreement and is intended for the following customers:
Customers who are Microsoft Visual Basic 6.0 and/or Microsoft Visual Studio 6.0 licensees.
Customers who are not licensees of Microsoft Visual Basic 6.0 nor Microsoft Visual Studio 6.0 but are using older versions of the two Common Controls."
I think this means that to legally use this, yoyu must have a licensed version of an earlier version of Access (say A2003) on your system.
If so that has been replaced with the Data Picker available in any Text Box wherein the Control Source is a DataTime Data Type.
From that KB:
"This package is provided under the terms of the End User License Agreement and is intended for the following customers:
Customers who are Microsoft Visual Basic 6.0 and/or Microsoft Visual Studio 6.0 licensees.
Customers who are not licensees of Microsoft Visual Basic 6.0 nor Microsoft Visual Studio 6.0 but are using older versions of the two Common Controls."
I think this means that to legally use this, yoyu must have a licensed version of an earlier version of Access (say A2003) on your system.
I'd disagree with Joe's last comment. I think it means that you can use it if the control was added in a database developed using a licensed version. This allows an upgrade path despite whoever held the original license.
I do not believe you have to be the license holder.
I would agree that you cannot download the dll and use it to insert a control into an Access 2007 or later database for the first time.
Kelvin
Kelvin
I do not believe you have to be the license holder.
I would agree that you cannot download the dll and use it to insert a control into an Access 2007 or later database for the first time.
Kelvin
Kelvin
Of course you have to be a license holder. MSFT has never, to my knowledge, removed the restriction that you must own a valid license to deploy this control. I could be wrong (and I'd love to see the MSFT announcement of that), but from my viewpoint Joe is right, and you can only deploy this control if you were previously licensed to deploy it.
AFAIK, the Calender Control was licensed through VB 5.0 and 6.0, and through certain versions of Access (the Developer Editions) - and those Dev editions contained a particular version of the control, not the same one that was provided with VB.
AFAIK, the Calender Control was licensed through VB 5.0 and 6.0, and through certain versions of Access (the Developer Editions) - and those Dev editions contained a particular version of the control, not the same one that was provided with VB.
ASKER
I originally used Microsoft Office Access 2003 (11.8321.8405) SP3 for my application and I now use
Microsoft Access Version 14.0.7145.5000 (32-bit) for this application.
I am also using Windows 7.
The application I am working with does not use the Calendar Control.
Microsoft Access Version 14.0.7145.5000 (32-bit) for this application.
I am also using Windows 7.
The application I am working with does not use the Calendar Control.
ASKER
The application works successfully when I open it in Access 2003.
The errors occur when I open the same MDB type application in Access 2010.
The errors occur when I open the same MDB type application in Access 2010.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
https://www.microsoft.com/en-us/download/details.aspx?id=10019
Kelvin