Common Dialog control in Office 2K

[Jerry]

I wrote an app in access 2003 using comdlg32.dll to
display the dialog box. When I send it to a user using
office 2K, Win 2K it gives a library not found error.
I don't have a path in my api call. The user has
comdlg32.dll but a different version.

Thank you for any help
Jerry

 

[Allen Browne]

That's quite typical of this control.

The only way to get a stable result across versions is to avoid using the
common dialog. For example, if you want the FileOpen/FileSave dialog, see:
http://www.mvps.org/access/api/api0001.htm

 

[Douglas J. Steele]

You mention comdlg32.dll in your text, but you've got Common Dialog control
in the subject. Are you making API calls, or are you, in fact, using
comdlg32.ocx, the Common Dialog control?

The control is problematic, so that most of us recommend not using it, but
making API calls. There's a complete code sample, courtesy of Ken Getz, as
http://www.mvps.org/access/api/api0001.htm at "The Access Web".

 

[Jerry]

Doug,
I'm sorry for the title. I'm using the comdlg32.dll in
an API call already. But when my user at another building
tries using it she gets a library not found error. I
can't add or remove any componants. I had her send me her
version of the comdlg32.dll file and the versions are a
bit off but she still has the file on her system. Her file
is in the WINNT/System32 and mine is Windows/System32.

Thanks for your help
Jerry

 

[Douglas J. Steele]

I've never heard of that being a problem before.

How are you declaring comdlg32.dll? Something along the lines of:

Declare Function aht_apiGetOpenFileName Lib "comdlg32.dll" _
Alias "GetOpenFileNameA" (OFN As tagOPENFILENAME) As Boolean

?

Assuming so, what is the Path on her machine? Is WinNT/System32 in it? (It's
possible her machine is misconfigured)