Niall,
I have not tried or even know how to deal with COM objects in WiTango.
I do know that Crystal no longer supports them. Crystal recomends you use
the Report Developer Component.
CR has a web server component you can install on your web server to run
reports w/o modification. You access your report as a URL and the browser
needs the CR plugin. It is easy to use, nothing special needed except $$$$.
The developers version of CR comes w/ a 5 user version of the web server
component. It costs around $1000/concurrent user after 5.
I have written an EXE using VB and the CR RDC that allows you to run a CR
from the command line and automatically generate a pdf. If you have the
developers version of CR version 8.5 with the RDC component installed on
your web server, you could probably call this exe from WiTango, generate a
pdf file, and then have the browser pull up the file you created. I am not
sure where this method of using CR would fall in their licensing agreement.
I am sure it would be in the gray area.
If you are interested in it, send me a private e-mail to
[EMAIL PROTECTED] and we can work something out.
Troy Sosamon
Denver, Co.
===== Original Message from [EMAIL PROTECTED] at 4/24/02 9:00 am
>Hi List
>
>Have a bit of a dilemma.
>
>I wrote a file in ASP and used the CrystalRuntime COM object. Got the
>thing working fine and I am now trying to get the thing working in Tango
>
>Standard thing tried to find the same COM object in the COM/DCOM pane and
>it doesnt show up. Bit strange because as I understand it Tango should be
>able to see the same objects as ASP etc etc
>
>Has anyone else had this problem or know of a work-around.
>
>TIA
>
>Niall
>
>
>________________________________________________________________________
>TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body