I'm using an access 97 and I have 5 activex controls on it
comdlg32.ocx, comctl32.ocx, imgedit.ocx, imgadmin.ocx, imgthumb.ocx. Problem
is I create an .mde using my development
PC and when I install and register the same ocx's on the client,
the .mde bombs because the references don't match. Any suggestions??

This probably won't help, but a Windows NT machine saves the files in a
different location then a Windows 9x.  NT saves in C:\Winnt\system32.
Windows 9x saves in C:\Windows\System.  Best thing to do is to put the
controls in the same folder as your app and regester them there.

--
HTH

Chris Nebinger

This probably is caused by a different version of one or more of those ocx
files, my guess is that comdlg32.ocx and comctl32.ocx are probably the
controls causing this problem.

Are you using ODE to distribute your app? If not, then you can't legally
just copy these MS controls across machine.  In any case, using CommonDialog
control isn't recommended especially since code alternatives are available.

Other than making absolutely sure that you are using a licensed copy of the
ocx and the versions are the same on both development and client machines,
you can only hope to "fix" the references on the fly.  You can try using
Terry Kreft's References Wizard available at www.mvps.org/access.

 -- Dev

I have an MDB in which you store the version number of your OCX/DLLs.
You then ship to the client where it compares the version number of
their OCX/DLLs and shows any differences.  If interested email me and
I'll email it to you.

Its my not so humble opinion that you the programmer need to keep the
latest OCX/DLLs on your system and ship to your clients.  And to heck
with any other software which requires older versions of the OCX/DLLs.
They'll just have to update thier software.

Tony
----
Message posted to newsgroup and, if appropriate, emailed.
Tony Toews, Independent Computer Consultant
Microsoft Access Links, Hints, Tips & Accounting Systems at
   http://www.granite.ab.ca/accsmstr.htm
VolStar http://www.volstar.com Manage hundreds or
   thousands of volunteers for special events.

Which doesn't work when called from an MDE because Access resolves the
references before it executes any code in the MDE.

Tony
----
Message posted to newsgroup and, if appropriate, emailed.
Tony Toews, Independent Computer Consultant
Microsoft Access Links, Hints, Tips & Accounting Systems at
   http://www.granite.ab.ca/accsmstr.htm
VolStar http://www.volstar.com Manage hundreds or
   thousands of volunteers for special events.

Tony, I remember you mentioning that renamingthe addin as .mde worked for
you, or did it?  I'll test it out the next vhance I get.

I'm Even more Confused?? In article Q194374 Microsoft. I'm
getting the error Function Isn't Available because of the Comctl32.ocx
But I have made both the development PC and the Clients PC the
same version of the .ocx. I'm using a VB 6.0 installation program to install
& register the lastest versions of these controls not the ODE.

No, but in order to use an addin in an MDE I had to make the addin an
MDE also.  Possibly thats what you were thinking of?

Tony
----
Message posted to newsgroup and, if appropriate, emailed.
Tony Toews, Independent Computer Consultant
Microsoft Access Links, Hints, Tips & Accounting Systems at
   http://www.granite.ab.ca/accsmstr.htm
VolStar http://www.volstar.com Manage hundreds or
   thousands of volunteers for special events.