Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 1888 - Use of TeeGrid with AureliusDataset causes problems with EOF
Summary: Use of TeeGrid with AureliusDataset causes problems with EOF
Status: RESOLVED DUPLICATE of bug 1850
Alias: None
Product: TeeGrid for Delphi
Classification: Unclassified
Component: Grid (show other bugs)
Version: unspecified
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: david berneda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-11 08:31 EDT by Roland Kossow
Modified: 2017-07-17 10:31 EDT (History)
1 user (show)

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Kossow 2017-07-11 08:31:15 EDT 
I have a project in which I use a TeeGrid with a Datasource that is an Aurelius Dataset.
When I try to itterate through the Aurelius Dataset, the Next method of the dataset is not movinf the recordcursor, so that I never get an EOF = True.
Is this a known issue?
Comment 1 Roland Kossow 2017-07-11 08:35:50 EDT 
The current workaround is to set Datasource of the TeeGrid to nil and after itterating through the Aurelisu dataset to set it to the dataset again which is not really cool :-)
Comment 2 Roland Kossow 2017-07-11 09:36:01 EDT 
To be honest. This bug is no problem if one codes good.
That means it is no problem if I disable controls of the Aurelius dataset and enable them after my walking through the records.
But IMO it should also work without the disabling.
Comment 3 yeray alonso 2017-07-17 06:53:45 EDT 
I believe this was fixed with http://bugs.teechart.net/show_bug.cgi?id=1850 and http://bugs.teechart.net/show_bug.cgi?id=1851

*** This bug has been marked as a duplicate of bug 1850 ***
Comment 4 Roland Kossow 2017-07-17 10:31:07 EDT 
But it is not fixed in the current version.