Connecting Tech Pros Worldwide Forums | Help | Site Map

Viewing COMDLG32 from an ASP page issues

Mike R
Guest
 
Posts: n/a
#1: Jul 19 '05
We have an ASP page that generates a report. We have
included a button on the page that allows the user to
save the report as a .csv file. The button makes use of
the Microsoft Common Dialog Control to display a "Save
As." dialog. This works perfectly. However once I send
the code to the client it seems to only work on some of
their machines and not others. Within the object
definition on the ASP page I've added the codebase
attribute and if the control is not present on the client
machine the user is prompted and the control is
downloaded from Microsoft. The ActiveX control however
does not appear to run. I've tried to replicate this
problem on my machine by changing the IE security
settings and I receive a message that informs me that my
setting don't allow ActiveX controls to run etc. On the
client site there is no message and all the ActiveX
security settings are set to "allow". I've tried removing
and re-registering the control but it seems to make no
difference. The control is definitely being downloaded
and registered by the codebase attribute but that seems
to be where it stops.

Thanks

Ray at
Guest
 
Posts: n/a
#2: Jul 19 '05

re: Viewing COMDLG32 from an ASP page issues


This is a client side issue. I suggest posting in an ActiveX group or an IE
group. ASP has no use of the common dialog control, since it's a
server-side technology that is interfaceless.

Ray at work

"Mike R" <MR@MR.com> wrote in message
news:138f01c38c06$ee8609c0$a301280a@phx.gbl...[color=blue]
> We have an ASP page that generates a report. We have
> included a button on the page that allows the user to
> save the report as a .csv file. The button makes use of
> the Microsoft Common Dialog Control to display a "Save
> As." dialog. This works perfectly. However once I send
> the code to the client it seems to only work on some of
> their machines and not others. Within the object
> definition on the ASP page I've added the codebase
> attribute and if the control is not present on the client
> machine the user is prompted and the control is
> downloaded from Microsoft. The ActiveX control however
> does not appear to run. I've tried to replicate this
> problem on my machine by changing the IE security
> settings and I receive a message that informs me that my
> setting don't allow ActiveX controls to run etc. On the
> client site there is no message and all the ActiveX
> security settings are set to "allow". I've tried removing
> and re-registering the control but it seems to make no
> difference. The control is definitely being downloaded
> and registered by the codebase attribute but that seems
> to be where it stops.
>
> Thanks[/color]


Niall Merrigan
Guest
 
Posts: n/a
#3: Jul 19 '05

re: Viewing COMDLG32 from an ASP page issues


Hi

Right if you look in the Temporary Internet Files for a page that starts
something like this ?Error and the CLSID of your control it will tell you
what went wrong. That can show where the install went wrong

HTH

Niall


"Mike R" <MR@MR.com> wrote in message
news:138f01c38c06$ee8609c0$a301280a@phx.gbl...[color=blue]
> We have an ASP page that generates a report. We have
> included a button on the page that allows the user to
> save the report as a .csv file. The button makes use of
> the Microsoft Common Dialog Control to display a "Save
> As." dialog. This works perfectly. However once I send
> the code to the client it seems to only work on some of
> their machines and not others. Within the object
> definition on the ASP page I've added the codebase
> attribute and if the control is not present on the client
> machine the user is prompted and the control is
> downloaded from Microsoft. The ActiveX control however
> does not appear to run. I've tried to replicate this
> problem on my machine by changing the IE security
> settings and I receive a message that informs me that my
> setting don't allow ActiveX controls to run etc. On the
> client site there is no message and all the ActiveX
> security settings are set to "allow". I've tried removing
> and re-registering the control but it seems to make no
> difference. The control is definitely being downloaded
> and registered by the codebase attribute but that seems
> to be where it stops.
>
> Thanks[/color]


Closed Thread