Common Dialog Control

[MikeBromley]

I am converting an existing Access 97 application to Access 2003. I've
converted the database and accompanying VB code and recompiled. Without any
modifications, the application fails where it used to opne a dialog to obtain
a file name to write to. Specifically, objCommonDialog is used to get a file
name for output of a new database name. The error says "Error (429) ActiveX
component cannot create object" I have made certain that References are
check-boxed, that is, Microsoft Common Dialog Control 6.0. I do not know
what else to do. On the same computer, that application runs fine in Access
97 Runtime with comdlg32.ocx in the Runtime directory. Any help would be
GREATLY appreciated.

Regards,
Mike Bromley

 

[Klatuu]

Here is a much better way to do what you are doing without having to use an
ActiveX control:

http://www.mvps.org/access/api/api0001.htm

 

[MikeBromley]

Thank you, so much. I had seen that, but was hoping to avoid changing the
codeas I don't know how many places it is used, but I will try it.
Mike Bromley

 

[Klatuu]

In the long run, it is worth it.

Thank you, so much. I had seen that, but was hoping to avoid changing the
codeas I don't know how many places it is used, but I will try it.
Mike Bromley

 

[MikeBromley]

I agree with you and I will implement this API in the next release. However,
in this release I simply wanted to convert this app from Acc97 to ACC 2003.
It is a runtime app and the former developer is long gone. So, I have to
maintain it, but I don't have Acc 97, hence the need to convert. For this
first release under Acc 2003, is there something else I can do? The code is
workable code, the ActiveX Control is supported, and I have a short time-line
for this release. I have purchased Visual Studio Tools for Developers, but
that hsn't yet been installed. Aside from allowing me to distribute the
runtime "flavor" of this app, will that product help of fix the problem?
Thanks again for putiing up with my stubborness, I appreciate your time.

 

[Klatuu]

I don't know if it will or not. As to making the ActiveX control work for
now, I am not strong on that. I think you have to register the control, but
I don't know the procedure for that.

I would suggest a new post with a header like.

How To Register an ActiveX control?

That way, your question is clear and you should get multiple reponses from
those who know how.

My problem is I only ever tried to use an ActiveX control one time and it
was so much trouble I decided it wasn't worth the headaches. I had problems
moving it to other system, there was no documentation to tell me what to
pass, what the options were, or what to expect it to return.

 

[MikeBromley]

Thanks for your time, Klatuu. I know how to register an ActiveX Control, and
it is already registered. I am thinking that this has something to do with
my computer registry allowing execution of safe or unsafe ActiveX Controls.
To fix that, I would need to edit the Registry, which I refuse to do. For
now, I'm going to wait for my Visual Studio Tools for Developers product,
install it, and see if that helps. There are a several good articles
involving Error 429 debug etc. by Allan Browne. Thanks again, have a great
summer.