When I run it I get an
unlicensed control error.


But he also said he has a license problem. this control apparenty requires
a redistribution license for it to run in Design time - think he needs to go
to the API directly if he must use the common dialogs controls.

Regards,
Tom Ogilvy


"Harald Staff" wrote in message
...
You will have to do nothing. It works on your system. The trouble with
external components
like .OCX and .DLL files is that every user will need them installed AND
properly
registered -that's what Setup programs do.

So you can install comdlg.ocx at all your users' systems -and make sure
it's done
everytime they upgrade systems or os'es -or you can use what's already in
there, like
GetOpenFilename in VBA. Both solutions work, but the first one is
troublesome and should
be used only when really needed. Add to this that most users can't perform
these
installations on the latest Windows versions, they need someone from the
system
administration to do it for them with their secret cowboy passwords. XP is
soooo safe, you
know.

Heard the phrase "DLL hell" ? This is what it's about. I live there and
hate it beyond
civilized description.

--
HTH. Best wishes Harald
Excel MVP

Followup to newsgroup only please.

";-)" wrote in message
...
Ok, thanks.

But shouldn't comdlg32.ocx (I use in VB often) work too?

Why would trying comdlg32.ocx cause other excel sheets to fail?

Will I have to reload Office?