Subject | Re: [IBO] Cannot Prepare a blank statement error |
---|---|
Author | Antti Kurenniemi |
Post date | 2009-03-10T17:12:33Z |
I have a similar problem occurring every now and then (and never in
debugging of course), with FastReports. I think my problem might be because
there are query components of the same name on different forms (qryHeader),
and the report system identifies it's queries just by name, not "full path"
of name like form.component, but I am not sure yet. Could you have some
similar situation?
Antti Kurenniemi
debugging of course), with FastReports. I think my problem might be because
there are query components of the same name on different forms (qryHeader),
and the report system identifies it's queries just by name, not "full path"
of name like form.component, but I am not sure yet. Could you have some
similar situation?
Antti Kurenniemi
----- Original Message -----
From: "acathelp" <acathelp@...>
To: <IBObjects@yahoogroups.com>
Sent: Tuesday, March 10, 2009 5:38 PM
Subject: Re: [IBO] Cannot Prepare a blank statement error
>I have narrowed down when the error is occuring, but I'm not sure what to
>do to fix it. The code for TIB_BDataset.SysPrepareSQL executes without
>issue when I first click the button to build the SQL for the report (I use
>SQL.Append by the way), then the Rave component executes its code for the
>report, followed by another call to TIB_BDataset.SysPrepareSQL which fails
>with the Empty dataset error message.
>
> I have put Showmessage statements in the IB_Components code to determine
> that the SQL.Text is indeed completely empty upon the 2nd time through,
> but I've never seen this happen before. I reinstalled my IBO components
> again just in case, but didn't help.
>
> At this point I can't be sure if this is an IBO issue or an issue with
> Rave reports. The strange thing is that the underlying Delphi project
> code hasn't changed, only the reinstallation of the software. Any ideas
> are welcome, as this is now happening to several reports, so it rules out
> a single "report file" issue.
>
> Thanks again,
>
> Nick
>