Subject | Re: [IBO] IBO 4.2 Gc with D3 and Report Builder |
---|---|
Author | andre2405 |
Post date | 2002-04-09T02:59:59Z |
--- In IBObjects@y..., Geoff Worboys <geoff@t...> wrote:
the latest I think. I use D3 'cause I have to use it. RB 4.x is the
latest version available for D3.
callstack. I just get an empty window. If you can advise me it would
be fine. If I trace query.close and I haven't open the report I can
get through many lines of code. If I open the report before, the
error occurs directly at query.close. I really don't know what to do
now:(
nil makes no changes. If I close the query while the report is still
open the error occurs too.
thx a lot for your answer!
cu Andre
> Andre,will
>
> Given your mix of versions I doubt very much if anyone else here
> be able to reproduce your problem exactly. I dont have Delphi3, II don't use a mix of versions. I'm using IBO 4.2 Gc, this should be
> probably have a copy of RB4 somewhere in my archives but dont have
> time to try an reinstall for just this purpose.
the latest I think. I use D3 'cause I have to use it. RB 4.x is the
latest version available for D3.
> I suggest that you take a detailed look at the callstack when theI tried to find the problem myself. I don't know to work with the
> exception occurs - this will generally give you some hint as to what
> particular component is giving problems. Once you have worked out
> which component/method then a breakpoint may allow you to discover
> exactly which property is involved - and this may let you work out
> how to work around the problem.
callstack. I just get an empty window. If you can advise me it would
be fine. If I trace query.close and I haven't open the report I can
get through many lines of code. If I open the report before, the
error occurs directly at query.close. I really don't know what to do
now:(
> That is to say. I expect the problem is specific to your versionI'm absolutely shure this is a problem of IBO 4 and RB 4.
> combination (I am using RB5 with IBO4 and Delphi5 without any such
> problems). I suspect you will need to find a work around for the
> problem.
> Such a work around may include closing or unpreparing the querybefore
> closing the report, or perhaps disconnecting the query from thegood
> report. Lots of possibilities and probably only some patience and
> investigative debugging will reveal what needs to be done.I tried a lot of things. Closing the query or setting the dataset to
nil makes no changes. If I close the query while the report is still
open the error occurs too.
thx a lot for your answer!
cu Andre