Stumper - Cannot open dataset
Report that worked fine under D3, ported to D5 RBuilder 6.02
I am getting a Cannot Open Dataset. But wait, it's not as simple as you
might think.
Using CodeSite to output the Report, DBPipeline and Datasource, everything
is hooked up.
Using a grid, the dataset is populated, right before print.
There is only one PipeLine and one DataSet. The DataSet is a RxMemoryData,
but I haven't had this problem with them before and I've used them attached
to RBuilder reports many times.
So, I drop a new report, attach it to the DataPipeline and add one and only
one field into the detail section. I disconnect the old report and run
printing the new report. Same error message.
So, it's definately not a break in the chain, the dataset is definitely
populated, there are no filters running and the dataset is definitely open
the line before the report print is called and it reproduces with a brand
spanking new report.
Any other ideas?
John
I am getting a Cannot Open Dataset. But wait, it's not as simple as you
might think.
Using CodeSite to output the Report, DBPipeline and Datasource, everything
is hooked up.
Using a grid, the dataset is populated, right before print.
There is only one PipeLine and one DataSet. The DataSet is a RxMemoryData,
but I haven't had this problem with them before and I've used them attached
to RBuilder reports many times.
So, I drop a new report, attach it to the DataPipeline and add one and only
one field into the detail section. I disconnect the old report and run
printing the new report. Same error message.
So, it's definately not a break in the chain, the dataset is definitely
populated, there are no filters running and the dataset is definitely open
the line before the report print is called and it reproduces with a brand
spanking new report.
Any other ideas?
John
This discussion has been closed.
Comments
In RBuilder 4.x, a report would print just fine if the dataset had called
DisableControls.
In RBuilder 6.x, if a dataset does not have controls enabled it give the
Cannot open dataset error, which is highly misleading.
John