Which way of calling the Common Dialog

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Which way of calling the common dialog box is more reliable? Using the
Active X or the windows API? When I use the Active X, it's not much coding
and simple to use. I have never used the API, but every now and then, the
Active X acts up, and now my cmdl is dead? Can anyone explain to me why the
active X just went dead if I didn't change anything in my code? Thanks.
 
Kou said:
Which way of calling the common dialog box is more reliable? Using the
Active X or the windows API? When I use the Active X, it's not much coding
and simple to use. I have never used the API, but every now and then, the
Active X acts up, and now my cmdl is dead? Can anyone explain to me why the
active X just went dead if I didn't change anything in my code? Thanks.
Click to expand...


There are probably lots of reasons, but I've never gotten by
the DLL Hell issue. It's just that every app that uses the
bleeping thing installs a different version and breaks all
the other apps that use it.

BTW, the API (that I think you're talking about) does not
use the common dialog, it uses Window's File browse
thingie, which is way more stable ;-)
 
Back
Top