Hi Tracey,
The API code at
www.mvps.org/access doesn't need any additional licence
or tools, and unlike the common dialog control is not prone to dll
version problems.
The compile error may well indicate a problem with references in your
database or VBA project. Here - courtesy of Douglas J. Steele MVP
- is how to check out that possibility:
------
Open any code module (or open the Immediate Window,
using Ctrl-G, provided you haven't selected the "keep
debug window on top" option). Select Tools |
References from the menu bar. Examine all of the selected
references.
If any of the selected references have "MISSING:" in
front of them, unselect them, and back out of the dialog.
If you really need the reference(s) you just unselected
(you can tell by doing a Compile All Modules), go back
in and reselect them.
If none have "MISSING:", select an additional reference
at random, back out of the dialog, then go back in and
unselect the reference you just added. If that doesn't
solve the problem, try to unselect as many of the
selected references as you can (Access may not let you
unselect them all), back out of the dialog, then go back
in and reselect the references you just unselected.
(NOTE: write down what the references are before you
delete them, because they'll be in a different order
when you go back in).
Just so you know: the problem will occur even if the
library that contains the specific function that's
failing doesn't have a problem.
----
If that is not the problem, please post back here and include the line
of code that is causing the compile error.
I tried this and I got a compile error that the user
datatype was not defined. Is an additional license
required to ues this function? Do I need developer tools
or VB license to use this? I tried to find the Microsoft
common dialogs control (as in previous version of access)
and I could not find it. Has the name or control changed?
John Nurick [Microsoft Access MVP]
Please respond in the newgroup and not by email.
