I developed a Excel sheet on my home PC, XP pro, Office XP, VB 6 installed
too.

The sheet works fine on my system.

I have one user form that opens when opened. I use a reference to
comdlg32.ocx (MS Common Dialog Control Version 6.0) to allow me to have a
file selection tool.

On the client system (large Corp) Win 2K, Office 2000. I can't get it to
work. I even copied all parts over as text and recreated the Sheet. On the
client system, If I don't set the "References" first when I add this control
to the tool bar I get a control that is named "Unknown". If I set the
Reference first, then add to control, it looks fine. When I run it I get an
unlicensed control error.

I have also noticed that after fighting this problem the system as lost the
ability to open any of the older excel sheets.

SO can I use this OCX with out loading VB 6 on it? Is there a "legal"
control that does the same thing? Will I have to reload Office to fix the
functioning of the older sheets?

application.getopenfilename


tim


";-)" wrote in message
...
I developed a Excel sheet on my home PC, XP pro, Office XP, VB 6 installed
too.

The sheet works fine on my system.

I have one user form that opens when opened. I use a reference to
comdlg32.ocx (MS Common Dialog Control Version 6.0) to allow me to have a
file selection tool.

On the client system (large Corp) Win 2K, Office 2000. I can't get it to
work. I even copied all parts over as text and recreated the Sheet. On
the
client system, If I don't set the "References" first when I add this
control
to the tool bar I get a control that is named "Unknown". If I set the
Reference first, then add to control, it looks fine. When I run it I get
an
unlicensed control error.

I have also noticed that after fighting this problem the system as lost
the
ability to open any of the older excel sheets.

SO can I use this OCX with out loading VB 6 on it? Is there a "legal"
control that does the same thing? Will I have to reload Office to fix the
functioning of the older sheets?

Wouldn't this open an excel sheet? I need to get a data file name.


"Tim Williams" <saxifrax@pacbell*dot*net wrote in message
...
application.getopenfilename


tim


";-)" wrote in message
...
I developed a Excel sheet on my home PC, XP pro, Office XP, VB 6
installed
too.

The sheet works fine on my system.

I have one user form that opens when opened. I use a reference to
comdlg32.ocx (MS Common Dialog Control Version 6.0) to allow me to have
a
file selection tool.

On the client system (large Corp) Win 2K, Office 2000. I can't get it
to
work. I even copied all parts over as text and recreated the Sheet. On
the
client system, If I don't set the "References" first when I add this
control
to the tool bar I get a control that is named "Unknown". If I set the
Reference first, then add to control, it looks fine. When I run it I
get
an
unlicensed control error.

I have also noticed that after fighting this problem the system as lost
the
ability to open any of the older excel sheets.

SO can I use this OCX with out loading VB 6 on it? Is there a "legal"
control that does the same thing? Will I have to reload Office to fix
the
functioning of the older sheets?

Just for added clarity:

GetOpenFilename just returns the name (fully qualified with path) of the
file selected - it doesn't open it. The user can select any type of file.
(if multiselect is set to true, it returns an array of filenames selected by
the user).

--
Regards,
Tom Ogilvy

";-)" wrote in message
...
Wouldn't this open an excel sheet? I need to get a data file name.


"Tim Williams" <saxifrax@pacbell*dot*net wrote in message
...
application.getopenfilename


tim


";-)" wrote in message
...
I developed a Excel sheet on my home PC, XP pro, Office XP, VB 6
installed
too.

The sheet works fine on my system.

I have one user form that opens when opened. I use a reference to
comdlg32.ocx (MS Common Dialog Control Version 6.0) to allow me to
have
a
file selection tool.

On the client system (large Corp) Win 2K, Office 2000. I can't get it
to
work. I even copied all parts over as text and recreated the Sheet.
On
the
client system, If I don't set the "References" first when I add this
control
to the tool bar I get a control that is named "Unknown". If I set the
Reference first, then add to control, it looks fine. When I run it I
get
an
unlicensed control error.

I have also noticed that after fighting this problem the system as
lost
the
ability to open any of the older excel sheets.

SO can I use this OCX with out loading VB 6 on it? Is there a "legal"
control that does the same thing? Will I have to reload Office to fix
the
functioning of the older sheets?

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?

"Tom Ogilvy" wrote in message
...
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.

Ouch ! Yes, right. I've had that one with Comctl32.ocx, creating Watson errors, piracy
warnings and other fun things onto NT family computers. I removed the thing the thing
completely (it's a form statusbar) from all my work, made my own similar control instead,
and I have no idea what was/is wrong. One can't win those fights anyway.

Best wishes Harald
Excel MVP

Followup to newsgroup only please.