FetchData Event not firing

Posted by: francisdeleon on 4 August 2017, 2:53 pm EST

  • Posted 4 August 2017, 2:53 pm EST

    I have a dll created using VB6 that creates a report for display on a browser. The dll works fine on a Windows XP machine. However, I am having problems when the dll is deployed on a Windows 2000 Server. I traced the problem and found that the FetchData event is not firing.


    Has anybody encountered this problem? Why is the event not firing?

  • Replied 4 August 2017, 2:53 pm EST

    Francis,


    How are you checking whether the Fetch Data Event is firing or not?

  • Replied 4 August 2017, 2:53 pm EST

    I have a general purpose routine that writes to a log file. I call this routine with the message I wanted logged as a parameter. At the start of the FetchData subroutine, I called this routine with a simple message that the program entered the subroutine. No entries were added to the log file indicating that the program entered the FetchData subroutine. However, when the same program is ran on a Windows XP machine, the message is present in the log file indicating that the program entered the subroutine. The program was also installed on a Windows NT machine and no problems were ever reported by the users there.

  • Replied 4 August 2017, 2:53 pm EST

    Francis,


    The report may be throwing an error on this machine before reaching the Fetch Data event. Do any other events fire? By default, Active Reports uses the default pages settings of the default print driver for determining the dimensions to render the report in. If you are not setting the PrinterName property to a null string (which is recommended for web applications) and using a custom papersize than the report may work on your other machines which may have a print driver installed, and not on the 2000 machine, which may not have the print driver installed. Another problem could be related to permissions on this machine, or the assembly versions. There is not any reason why the Fetch Data would fire on one machine and not the others, unless an error is being thrown and the report is failing before this event.

  • Replied 4 August 2017, 2:53 pm EST

    We are not using ActiveReports for .Net. There is no PrinterName property available to us. We set the Printer.Device to a null string. We also trap for errors and we are not receiving any. I doubt that it is the assembly version as we use the same installer. I do not see how this problem could be related to permissions.
Need extra support?

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

Learn More

Forum Channels