Could not open dataset: DBPipeline1

rbuser

I have recently added some 'canned' reports to the End User framework of
an application that I am developing. I have created a report along the
lines of a demo provided with RB that uses the AutoSearch functionality
to set SQL parameters (..\Demos\5. AutoSearch\1. AutoSearch Field to SQL
Params).

All works fine on my development machine. I have sent a copy to a
tester. On his machine, he gets the following error:

Cannot generate report.
Could not open dataset.: DBPipeline1.

The query is bound to the same database object that is used in the end
user framework which is enabled at login time. He continues to be able
to design and run queries in the end user framework, so all seems fine
with the database object.

I have tried adding a few crude ShowMessage statements, it shows that it
is trying to open the right query to the right database (and that the
database is active), but I still get the error above.

Stuck and hoping for ideas.

Thanks in advance.


Bob McClintock

digitalmetaphors

Are you using the report on the form or are you loading templates for the
canned reports? Was the template saved with a datapipeline name of
ppDBPipeline1, or does ppDBPipeline1 exist on the form? We'll need more
information from you in order to figure this out.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

I am using a report on the form. ppDBPipeline1 does exist on the form.

So, in other words:

I have a report that has a pipeline property with a pipeline on the form.
I have a pipeline with a datasource property with a datasource on the form.
I have a datasource with a dataset property with a query on the form.

The query has parameters that are substituted at runtime using code similar
to the code in the demo I mentioned in my original posting to create an
autosearch dialog.

The report works fine on my machine.


I am using:

Delphi 6 Update pack 2
ReportBuilder 6.03

Both my machine and the target machine are Windows 2000 service pack 2.
The target machine is running a slightly older version of BDE and I am
working on providing an updated version, but as all other data access seems
to be working well, it does not seem likely to me that this is the cause of
the problem.

digitalmetaphors

You could also test without ReportBuilder involved. Create a new app with
the data access components on the form. Place a TDBGrid on the form. If
you install this new exe on the tester's machine, can you see the data in
the grid?


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Thanks, Jim I was essentially doing this very thing when you responded.
Looks like I have narrowed down the problem and it is not related to
ReportBuilder. The database driver the target machine is using is barfing
on parameter substitution. When the Query is opened, an exception is
being thrown with a message ('Operation not applicable'). For whatever
reason, this exception was being caught and not surfaced to the
application, so the only error I was seeing was the DBPipeline error.

Sorry for the waste of bandwidth, thanks for your help and quick response.