File Dialog Box

  • Thread starter Thread starter Beth
  • Start date Start date
B

Beth

I am using Access 2000 Developer to create an mde application that will run
in Access runtime. I have included the file dialog selector box in several
places so my users can select file locations instead of having to type them.
I have read several articles stating that the file dialog box won't work in
mde or runtime appliations. It is working fine in my mdb and also when I
convert the file to an mde. If I launch it on my development machine in
runtime it works. This seems to conflict with the articles.
When I try to run the same application on another machine it doesn't work
(matching the articles).
Is there a system file I am missing on the other machines or is it a fluke
that it works on my development machine?

I really want to include this feature for my users. Is there another
option?
Thanks,
Beth
 
Your answer is here:
http://www.mvps.org/access/api/api0001.htm
It replaces the File Dialog Box.

The reason you are experiencing what you are is that it doesn't matter
whether it is an mdb or an mde. What matters is whether the File Dialog Box
is registered on the computer it is running on. The File Dialog Box is an
ActiveX control and may or may not be registered on all targe machines.
Given that users may not have the savy to register them and may not even have
them on their computer, distributing apps using ActiveX controls can be
troublesome. Be aware that if you think you want to distribute the DLLs for
the ActiveX component with your app, you are violating Microsoft Copyright
laws.

It wont be that hard to replace the calls to the File Dialog, the arguments
are pretty much the same.
 
Hi,
you should avoid the commondialog control.
Instead try to use an API call e.g.:
http://www.mvps.org/access/api/api0001.htm
http://www.mvps.org/access/api/api0002.htm
The problem with the common dialog control is that it is an active x control
which is version and reference dependent. You would need to use a
design-time license instead of the runtime license or find some other
workaround. The api's listed will work much better since they are not version
dependent.
HTH
Good luck
 
Thanks for the answers. I will use these examples and avoid the common
dialog control.
Beth
 
Back
Top