
Problem getting common dialog to appear in NT 4.0
You are not alone. I have the same problem with this function and am
looking for the solution too.
FYI, I have had other API calls work fine in Windows 95 and Access 97 and
fail in NT 4.0 sp3, but was able to trace the problem to an inconsistency
between type declarations in the Declare Function statement and the actual
Access Basic that calls the external function. Something as simple as
having a variable declared as an Integer in the Declare Function... and as
a Long in the calling Function works fine in Win 95 but not in NT. It
seems that Win 95 is very forgiving of what appears to be sloppy
programming, whereas NT is not. This may help you with other API calls
that are not working, but probably not with comdlg32.dll.
Let me know if you've found a fix!
Quote:
> I have code to find a file using the comdlg32.dll in an access 97
> application. I don't want the installation problems that come with the
use
> of the comdlg32.ocx. The problem is that the code works fine in win95
and
> win98 but not in NT 4.0(sp3). I don't receive an error in NT it just
will
> not show the dialog. Does any one know of any issues with the
comdlg32.dll?
> Do I need to declare the api function any differently in NT? It does not
> make sense to me.
> Thomas Lane
> tushaus computer services