comdlg32.ocx and Access 2007

  • Thread starter Thread starter Zia Texas
  • Start date Start date
Z

Zia Texas

I have several Access databases that were originally written using an Access
version prior to Access 2007. I am in the process of converting the
databases and installing them on new machines running Win7 and Access 2007.

Over the years, one of the References I commonly used was comdlg32.ocx. It
does not appear that either Win7 or Access 2007 installs that particular
Active X file. I can copy it from an older machine, but that seems like a
strange solution.

Is comdlg32.ocx a "legacy" Active X file and has it been replaced with a
newer (and differently named) Active X fle? If so, what is the name of the
newer file?
 
Zia Texas said:
I have several Access databases that were originally written using an
Access
version prior to Access 2007. I am in the process of converting the
databases and installing them on new machines running Win7 and Access
2007.

Over the years, one of the References I commonly used was comdlg32.ocx.
It
does not appear that either Win7 or Access 2007 installs that particular
Active X file. I can copy it from an older machine, but that seems like a
strange solution.

Is comdlg32.ocx a "legacy" Active X file and has it been replaced with a
newer (and differently named) Active X fle? If so, what is the name of
the
newer file?
Click to expand...

Does this help?
http://social.answers.microsoft.com.../thread/f96acaa3-90d7-437a-a9cc-9130eb17fdb4/
 
Zia Texas said:
Is comdlg32.ocx a "legacy" Active X file and has it been replaced with a
newer (and differently named) Active X fle? If so, what is the name of the
newer file?
Click to expand...

Use the common dialog API calls as documented at the Access Web or the
MS Knowledge Base.
Call the standard Windows File Open/Save dialog box
http://www.mvps.org/access/api/api0001.htm
"ACC97: How to Use the Common Dialog API in an Access Database"
http://support.microsoft.com/?kbid=303066
While the article is in A97 the same code will work in newer versions
of Access

Note that the ocx is just a wrapper for these API calls.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
 
Paul:

Thanks for the information. However, it doesn't appear that MSCOMCTL.OCX is
a replacement for COMDLG32.OCX. From what I've found, they seem to do
different functions. Then again, I may have misunderstood the information on
the thread you cited.
 
Sorry, your are correct. I think when I searched I found a discussion on
issues with the common dialog control which referenced the solution I gave.
It could be that the same solution approach also works with the common
dialog control, if you want to try it. I would go with Tony's suggestion to
use the Windows API directly instead and eliminate the dependency. One
caveat is that Windows API code will need to be revisited to support 64-bit
Office 2010. I haven't addressed this yet in my code, but the issue has been
discussed on the Office 2010 website or blogs. The default Office 2010
installation is 32-bit, and then the API calls remain the same as they have
been.
 
Back
Top