designer object in web

Posted by: tomk10 on 4 August 2017, 2:54 pm EST

  • Posted 4 August 2017, 2:54 pm EST

    I have a DLL that returns a report designer object which I use with a call something like:


    Set ARV1.ReportSource = dsrObject


    How can I get this to work in a web interface?  I don't see a way to use this with the ReportServer.

  • Replied 4 August 2017, 2:54 pm EST

    They following KB article demonstrates how to use the ActiveX viewer over the web.
    http://www.datadynamics.com/forums/211/ShowPost.aspx

    There's also an example on our FTP site demonstrating how to stream reports to the client's browser:
    ftp://ftp.datadynamics.com/misc/AR2RDFOnTheWeb.zip
  • Replied 4 August 2017, 2:54 pm EST

    Thanks, but this is not any help.  I've reviewed all samples carefully.  In my project there is never a report file.  I am passing a DSR object directly to the ARViewer control in VB6.  I'm looking for a way to do the same with the web viewer.
  • Replied 4 August 2017, 2:54 pm EST

    You will need to save the DSR's layout as an RPX file for use on the web. Then load the RPX at runtime like the sample demonstrates.
  • Replied 4 August 2017, 2:54 pm EST

    Thanks again Brandon,


    I reviewed the AR2 Online ShowCase Samples in particular the "Simple Bound Report populated by ADO Data Control".  Since all my existing reports use an ADO control this is the best solution.  I have a few more issues that are giving me trouble. 


    First the connection string does not seem to work, that is it does not update the connection string saved with the control in the report file.  I am able generate a report as long as my valid connection is saved with the RPX but if I use that same string in the call:


     arptServer.ExportToByteArray("PDF",,cstr(strConnection))  is does not work


    Second, is there a way to filter the data with the bound control?  There is a SQL statement with the unbound example but if I use this method I will be forced to modify hundreds of reports and they will then be different that those used by the VB6 app (basically not an option)

  • Replied 4 August 2017, 2:54 pm EST

    You will need to modify the sample to work in your situation. The sample code isn't supposed to be a production-level application. Rather, it's a sample to help you get started in the ASP environment. You'll need to recompile the DLL with your changes in it.
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels