comdlg32.ocx and distributing an Access database 1

[blally]

I am working on a database that uses comdlg32.ocx (Microsoft Common Dialog). My problem is when I install this database on a Windows 95 or 98 machine I get a error in my code. I know how to fix the problem by going to tools and references while editing the code. This database was designed on a Windows 2000 machine so the database is looking for comdlg32.ocx in C:\winnt\system32. However, a Windows 95 or 98 machine stores the same file in C:\Windows\System.

I was wondering if there is a way to have the database look for comdlg32.ocx in both places so this does not have to be corrected each time I put the database on a different machine.

Brian

 

[DougP]

this is a "ruge goldberg" approach but...
create new folders in your '9x boxes that are C:\winnt\system32
and put comdlg32.ocx file in there
then it will find it.

Or maybe Not.

Sorry just a wild idea. DougP, MCP
dposton@universal1.com

Ask me how Bar-codes can help you be more productive.
Or visit my WEB site

http://www.barcodeone.com

 

[Francescina]

I fear that this brute force solution will not work because of the Windows Registry settings that indicate the OCX' location.
I suggest to deliver the database application together with the new OCX and let the setup procedure (I fear that the PDW will refuse this operation, you might need another installer program) install it on the machine and register in the Registry. Then everything will be fine.
The other solution (my preferred one) might be distributing two versions:
1. For Windows 2000 with the System32-reference
2. For older Win-versions with the System-reference.