TIBCQuery problem with NextDBGrid

Discussion of open issues, suggestions and bugs regarding IBDAC (InterBase Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
tsteinmaurer
Posts: 52
Joined: Thu 17 Dec 2009 08:25

TIBCQuery problem with NextDBGrid

Post by tsteinmaurer » Tue 02 Feb 2010 20:47

Hello,

I'm using NextDBGrid as data-aware grid component. In combination with TIBCQuery, I do get weird results when navigating through the result set in the grid, with e.g. the Page-Down key. The grid works fine with a TIBOQuery component from IBObjects.

I've created a small demo application, which looks like that upon start:
http://www.iblogmanager.com/download/mi ... /Clip1.jpg

Everything looks fine. Now I'm issuing a few Page-Downs in all grids. The left upper grid (which is a combination of TIBCQuery and TNextDBGrid) starts already messing up. See the gap between value 23 and 30.
http://www.iblogmanager.com/download/mi ... /Clip2.jpg

It's getting even worse when I'm at the bottom of the grid and then hold the Page-Down key for a second or two. This results in the following screen:
http://www.iblogmanager.com/download/mi ... /Clip3.jpg
See the gap between 230 and 623.

All other three combinations: TIBCQuery with TDBGrid, TIBOQuery with NextDBGrid and TDBGrid are working fine in all scenarios.

Any clues? Any property for TIBCQuery which might affect this issue?

Thanks!

Regards,
Thomas

Falcon
Devart Team
Posts: 19
Joined: Tue 02 Feb 2010 10:40

Post by Falcon » Thu 04 Feb 2010 12:21

There is no NextDBGrid trial version, so we can't reproduce this bug. Can you please ask BergSoft company this question?

tsteinmaurer
Posts: 52
Joined: Thu 17 Dec 2009 08:25

Post by tsteinmaurer » Thu 04 Feb 2010 14:01

Hi!

The author already knows about the problem.

NextDBGrid depends on an accurate RecordCount number, which isn't the case for TIBCQuery when using QueryRecCount := False (the default value). Setting QueryRecCount := True solves the problem with NextDBGrid, but may open another problem, namely it can produce an invalid SQL statement as result when using QueryRecCount. See my other thread "Problem with QueryRecCount option of TIBCQuery" from Feb. 3rd 2010.

Thanks,
Thomas

Post Reply