> I know this is not strictly VB,(it does involve Crystal and VBScript tho')
> but could someone confirm or deny something for me.
> We have recently upgraded to Crystal 9 on a test server, and cannot
> get any reports (saved in CR9 format) to work using the Crystal ActiveX
> viewer
> component on our ASP webpages (The same report in CR8 format
> works fine). On further investigation of the documentation, the
implication
> seems to be
> that CR9 reports are not compatable with the Crystal OCX viewer. It
> seems that you need to use the HTML viewer instead. Surely this cannot be
> true?!

> Is it true that the OCX is not compatable with CR9, ie can we no
> longer include the ActiveX report viewer on our ASP pages if we wish
> to use CR9?? If it is possible, could you please let us know what changes
> need to be made to our code. I can give you some examples of the existing
> code if you like.

> Thanks in advance,

> ChrisM

> Are you using the version 9 ActiveX Viewer (CRViewer9.dll)?  They have
> reguided the COM dll and its name is changed from crviewer.dll to
> crviewer9.dll.

> > I know this is not strictly VB,(it does involve Crystal and VBScript
tho')
> > but could someone confirm or deny something for me.
> > We have recently upgraded to Crystal 9 on a test server, and cannot
> > get any reports (saved in CR9 format) to work using the Crystal ActiveX
> > viewer
> > component on our ASP webpages (The same report in CR8 format
> > works fine). On further investigation of the documentation, the
> implication
> > seems to be
> > that CR9 reports are not compatable with the Crystal OCX viewer. It
> > seems that you need to use the HTML viewer instead. Surely this cannot
be
> > true?!

> > Is it true that the OCX is not compatable with CR9, ie can we no
> > longer include the ActiveX report viewer on our ASP pages if we wish
> > to use CR9?? If it is possible, could you please let us know what
changes
> > need to be made to our code. I can give you some examples of the
existing
> > code if you like.

> > Thanks in advance,

> > ChrisM

> I believe I am using the new version of the DLL. The code I have included
> into my page to reference the component is as follows:

> ...
> <OBJECT ID="CRViewer" CLASSID="CLSID:2DEF4530-8CE6-41C9-84B6-A54536C90213"
> WIDTH=100% HEIGHT=99%

> 2,0,442">
> ...

> Also, the component (which does display in the page) looks slightly
> different to the one I previously saw (Primarily it has 'Powered by
Crystal'
> in the top left hand corner)

> Have you actually got version 9 reports displaying in the ActiveX viewer?
If
> you have then it is just me. If you haven't, give it a go and see if you
can
> get it to work...

> Cheers,

> Chris.

> > Are you using the version 9 ActiveX Viewer (CRViewer9.dll)?  They have
> > reguided the COM dll and its name is changed from crviewer.dll to
> > crviewer9.dll.

> > > I know this is not strictly VB,(it does involve Crystal and VBScript
> tho')
> > > but could someone confirm or deny something for me.
> > > We have recently upgraded to Crystal 9 on a test server, and cannot
> > > get any reports (saved in CR9 format) to work using the Crystal
ActiveX
> > > viewer
> > > component on our ASP webpages (The same report in CR8 format
> > > works fine). On further investigation of the documentation, the
> > implication
> > > seems to be
> > > that CR9 reports are not compatable with the Crystal OCX viewer. It
> > > seems that you need to use the HTML viewer instead. Surely this cannot
> be
> > > true?!

> > > Is it true that the OCX is not compatable with CR9, ie can we no
> > > longer include the ActiveX report viewer on our ASP pages if we wish
> > > to use CR9?? If it is possible, could you please let us know what
> changes
> > > need to be made to our code. I can give you some examples of the
> existing
> > > code if you like.

> > > Thanks in advance,

> > > ChrisM

> Yes, 2DEF4530-8CE6-41C9-84B6-A54536C90213 is version 9 Viewer.  I have it
> working with the version reports, but I am using in the RDC and I did not
> try it on ASP.

> Actually, you just say it does not work using the version 9 viewer.  Do
you
> mean the viewer is loaded but does not show anything?  Can you use this
> viewer to display the version 8 reports then?

> K.

> > I believe I am using the new version of the DLL. The code I have
included
> > into my page to reference the component is as follows:

> > ...
> > <OBJECT ID="CRViewer"

> > WIDTH=100% HEIGHT=99%

> > 2,0,442">
> > ...

> > Also, the component (which does display in the page) looks slightly
> > different to the one I previously saw (Primarily it has 'Powered by
> Crystal'
> > in the top left hand corner)

> > Have you actually got version 9 reports displaying in the ActiveX
viewer?
> If
> > you have then it is just me. If you haven't, give it a go and see if you
> can
> > get it to work...

> > Cheers,

> > Chris.

> > > Are you using the version 9 ActiveX Viewer (CRViewer9.dll)?  They have
> > > reguided the COM dll and its name is changed from crviewer.dll to
> > > crviewer9.dll.

> > > > I know this is not strictly VB,(it does involve Crystal and VBScript
> > tho')
> > > > but could someone confirm or deny something for me.
> > > > We have recently upgraded to Crystal 9 on a test server, and cannot
> > > > get any reports (saved in CR9 format) to work using the Crystal
> ActiveX
> > > > viewer
> > > > component on our ASP webpages (The same report in CR8 format
> > > > works fine). On further investigation of the documentation, the
> > > implication
> > > > seems to be
> > > > that CR9 reports are not compatable with the Crystal OCX viewer. It
> > > > seems that you need to use the HTML viewer instead. Surely this
cannot
> > be
> > > > true?!

> > > > Is it true that the OCX is not compatable with CR9, ie can we no
> > > > longer include the ActiveX report viewer on our ASP pages if we wish
> > > > to use CR9?? If it is possible, could you please let us know what
> > changes
> > > > need to be made to our code. I can give you some examples of the
> > existing
> > > > code if you like.

> > > > Thanks in advance,

> > > > ChrisM

> Sorry if I was unclear. When I try to run the report, the viewer loads,
but
> then I get a message
>  'Unable to load report. [Connecting to Page Server: abcd.mydomain.com]

> The Page Server address is correct, and if I try to display a Crystal8
> report then it works fine. In fact I tried a CR8 report which worked OK,
> then without touching the code, I opened the report in CR9 and saved it
back
> (so that I changed the version it was saved as).  I then refreshed the
page,
> and got the error described above.

> There is an article at:
> http://support.crystaldecisions.com/library/kbase/articles/c2011677.asp

> which states
>      This error message appears because Crystal Reports 9
>      does not support the Crystal ActiveX (OCX) control.
>      Applications that use the OCX cannot run on computers
>      that have runtime files from Crystal Reports 9.

> So I guess that seems fairly clear, but I find it hard to believe that it
is
> simply not supported, especially since a version of the OCX ships with
> version 9!

> Maybe it's just me! but is doesn't make much sense.

> Regards,
> Chris.

> > Yes, 2DEF4530-8CE6-41C9-84B6-A54536C90213 is version 9 Viewer.  I have
it
> > working with the version reports, but I am using in the RDC and I did
not
> > try it on ASP.

> > Actually, you just say it does not work using the version 9 viewer.  Do
> you
> > mean the viewer is loaded but does not show anything?  Can you use this
> > viewer to display the version 8 reports then?

> > K.

> > > I believe I am using the new version of the DLL. The code I have
> included
> > > into my page to reference the component is as follows:

> > > ...
> > > <OBJECT ID="CRViewer"
> CLASSID="CLSID:2DEF4530-8CE6-41C9-84B6-A54536C90213"
> > > WIDTH=100% HEIGHT=99%

> > > 2,0,442">
> > > ...

> > > Also, the component (which does display in the page) looks slightly
> > > different to the one I previously saw (Primarily it has 'Powered by
> > Crystal'
> > > in the top left hand corner)

> > > Have you actually got version 9 reports displaying in the ActiveX
> viewer?
> > If
> > > you have then it is just me. If you haven't, give it a go and see if
you
> > can
> > > get it to work...

> > > Cheers,

> > > Chris.

> > > > Are you using the version 9 ActiveX Viewer (CRViewer9.dll)?  They
have
> > > > reguided the COM dll and its name is changed from crviewer.dll to
> > > > crviewer9.dll.

> > > > > I know this is not strictly VB,(it does involve Crystal and
VBScript
> > > tho')
> > > > > but could someone confirm or deny something for me.
> > > > > We have recently upgraded to Crystal 9 on a test server, and
cannot
> > > > > get any reports (saved in CR9 format) to work using the Crystal
> > ActiveX
> > > > > viewer
> > > > > component on our ASP webpages (The same report in CR8 format
> > > > > works fine). On further investigation of the documentation, the
> > > > implication
> > > > > seems to be
> > > > > that CR9 reports are not compatable with the Crystal OCX viewer.
It
> > > > > seems that you need to use the HTML viewer instead. Surely this
> cannot
> > > be
> > > > > true?!

> > > > > Is it true that the OCX is not compatable with CR9, ie can we no
> > > > > longer include the ActiveX report viewer on our ASP pages if we
wish
> > > > > to use CR9?? If it is possible, could you please let us know what
> > > changes
> > > > > need to be made to our code. I can give you some examples of the
> > > existing
> > > > > code if you like.

> > > > > Thanks in advance,

> > > > > ChrisM

> I think this article is talking about the old Crystal ActiveX Control, not
> the Crystal Smart Viewer (CRViewer9.dll) that you are using.  Are you
using
> the craxdrt9.dll (Crystal Report Run Time Library) on your server to load
> the report?

> > Sorry if I was unclear. When I try to run the report, the viewer loads,
> but
> > then I get a message
> >  'Unable to load report. [Connecting to Page Server: abcd.mydomain.com]

> > The Page Server address is correct, and if I try to display a Crystal8
> > report then it works fine. In fact I tried a CR8 report which worked OK,
> > then without touching the code, I opened the report in CR9 and saved it
> back
> > (so that I changed the version it was saved as).  I then refreshed the
> page,
> > and got the error described above.

> > There is an article at:
> > http://support.crystaldecisions.com/library/kbase/articles/c2011677.asp

> > which states
> >      This error message appears because Crystal Reports 9
> >      does not support the Crystal ActiveX (OCX) control.
> >      Applications that use the OCX cannot run on computers
> >      that have runtime files from Crystal Reports 9.

> > So I guess that seems fairly clear, but I find it hard to believe that
it
> is
> > simply not supported, especially since a version of the OCX ships with
> > version 9!

> > Maybe it's just me! but is doesn't make much sense.

> > Regards,
> > Chris.

> > > Yes, 2DEF4530-8CE6-41C9-84B6-A54536C90213 is version 9 Viewer.  I have
> it
> > > working with the version reports, but I am using in the RDC and I did
> not
> > > try it on ASP.

> > > Actually, you just say it does not work using the version 9 viewer.
Do
> > you
> > > mean the viewer is loaded but does not show anything?  Can you use
this
> > > viewer to display the version 8 reports then?

> > > K.

> > > > I believe I am using the new version of the DLL. The code I have
> > included
> > > > into my page to reference the component is as follows:

> > > > ...
> > > > <OBJECT ID="CRViewer"
> > CLASSID="CLSID:2DEF4530-8CE6-41C9-84B6-A54536C90213"
> > > > WIDTH=100% HEIGHT=99%

> > > > 2,0,442">
> > > > ...

> > > > Also, the component (which does display in the page) looks slightly
> > > > different to the one I previously saw (Primarily it has 'Powered by
> > > Crystal'
> > > > in the top left hand corner)

> > > > Have you actually got version 9 reports displaying in the ActiveX
> > viewer?
> > > If
> > > > you have then it is just me. If you haven't, give it a go and see if
> you
> > > can
> > > > get it to work...

> > > > Cheers,

> > > > Chris.

> > > > > Are you using the version 9 ActiveX Viewer (CRViewer9.dll)?  They
> have
> > > > > reguided the COM dll and its name is changed from crviewer.dll to
> > > > > crviewer9.dll.

> > > > > > I know this is not strictly VB,(it does involve Crystal and
> VBScript
> > > > tho')
> > > > > > but could someone confirm or deny something for me.
> > > > > > We have recently upgraded to Crystal 9 on a test server, and
> cannot
> > > > > > get any reports (saved in CR9 format) to work using the Crystal
> > > ActiveX
> > > > > > viewer
> > > > > > component on our ASP webpages (The same report in CR8 format
> > > > > > works fine). On further investigation of the documentation, the
> > > > > implication
> > > > > > seems to be
> > > > > > that CR9 reports are not compatable with the Crystal OCX viewer.
> It
> > > > > > seems that you need to use the HTML viewer instead. Surely this
> > cannot
> > > > be
> > > > > > true?!

> > > > > > Is it true that the OCX is not compatable with CR9, ie can we no
> > > > > > longer include the ActiveX report viewer on our ASP pages if we
> wish
> > > > > > to use CR9?? If it is possible, could you please let us know
what
> > > > changes
> > > > > > need to be made to our code. I can give you some examples of the
> > > > existing
> > > > > > code if you like.

> > > > > > Thanks in advance,

> > > > > > ChrisM