Michael Mullan
15-Mar-2010, 10:31 AM
Hi,
If I build a report on my development machine, and the customer tries to run it on their workstation, we get a rather ugly STATUS 72, crash and burn error.
Turns out that the runtime/integration does not automatically switch the datasource location for Embedded DB reports. This seems to be a Bad Idea. I expect that a report called from within a VDF program will use the dame Filelist.cfg and DataPath as the application that runs the report, unless the developer expressly forces it not to.
I had to install the VRW eval on the workstation to make it work.
MM.
If I build a report on my development machine, and the customer tries to run it on their workstation, we get a rather ugly STATUS 72, crash and burn error.
Turns out that the runtime/integration does not automatically switch the datasource location for Embedded DB reports. This seems to be a Bad Idea. I expect that a report called from within a VDF program will use the dame Filelist.cfg and DataPath as the application that runs the report, unless the developer expressly forces it not to.
I had to install the VRW eval on the workstation to make it work.
MM.