Liveware Publishing Support Forum

We have a Visual FoxPro 11 application which calls ReportWorks reports originally written in ReportWriter 6, which work fine.____I used ReportWorks 11 Designer to copy one of the original reports and modify it slightly, saving it with a new name. I also modified the FoxPro code to set parameters in the rrw32.ocx OLE Object for the new report.____The original reports run without any problems.____The new report gives an error when setting the ReportName= parameter property.__Exception code C0000005. OLE object may be corrupt.____Running ReportWorks 11.1.007 on XP Pro.____Any suggestions would be appreciated.____Dave Connolly__IT Shared Services__Province of Prince Edward Island__Canada__

Hopefully the 11.1.009 update will help.____Kathleen__R&R Support

Updated to version 11.1.09 and still getting same error, though it did seem to work once while using the debugger, although it is now giving the same error in the debugger.____Any other suggestions?__

I can sometimes get the ReportName= set to the new report (ppsarpt.rrw) I adapted from an existing report, and which is stored in the same directory (data) as the existing reports (which run without any problem).____When I hit the OK button to execute the report (set .Action = 1) the following error appears:____OLE IDispatch execption code 0 from rrw32: Cannot open file ^datappsarpt.rrw^..____Am I missing some feature of ReportWorks or MS Visual FoxPro to allow the Custom Control to run the newly created report?____Thanks again,____Dave Connolly__

I posted this question to a MSDN Foxpro newsgroup, and received a reply which indicated that the RRWRUN.EXE viewer from the recent ReportWorks versions works correctly with MS Visual FoxPro.____I tried one report which worked correctly via the viewer and will be converting the application to use RRWRUN.EXE rather than RRW32.OCX__