I've encountered a problem using cxGrid from DevExpress in which it appears
the selected row in the grid might not be accurately represented in the
underlying dataset.  I encountered the issue using a TEDBQuery component
with the grid.  I first thought it might be an issue with the TcxGrid but
tried to replicate the issue with an ADOCennection/ADOQuery and an Access
table and couldn't reproduce it that way.  Hence, my post here.

I've posted a sample project to the binaries newsgroup to demonstrate what
is happening (see Test567).  Realizing that you may not have the DevExpress
component available, I included an EXE within the project directory
(Test567.exe).  There is also a folder called "edb" which contains a test
edb database used by the project.  It should be configured in EDB Manager
with a database name of "TestDB567" before attempting to use the sample app.

In the sample there are two grids:  (1) on top is a standard TDBGrid and (2)
below this is a TcxGrid.  There is also a GroupBox with a button having a
caption of "Get Field from EDBQuery which places the value of the current
record into several TLabels using the TEDBQuery's FieldValues method.

To duplicate what I'm experiencing, click on one of the rows in the TcxGrid
(the lower of the two tables).  Note what row is selected.  Notice that a
different row is selected in the DBGrid (above).  When clicking on the "Get
Field from EDBQuery" button, the labels are filled with values from the row
highlighted in the DBGrid.

Again, I initially thought this might be a TcxGrid issue, but I couldn't
duplicate the problem with another database.  So, I'm posting here.  Does
anybody have any thoughts on this?

Greg,

<< I've encountered a problem using cxGrid from DevExpress in which it
appears the selected row in the grid might not be accurately represented in
the underlying dataset.  I encountered the issue using a TEDBQuery component
with the grid.  I first thought it might be an issue with the TcxGrid but
tried to replicate the issue with an ADOCennection/ADOQuery and an Access
table and couldn't reproduce it that way.  Hence, my post here.

I've posted a sample project to the binaries newsgroup to demonstrate what
is happening (see Test567).  Realizing that you may not have the DevExpress
component available, I included an EXE within the project directory
(Test567.exe).  There is also a folder called "edb" which contains a test
edb database used by the project.  It should be configured in EDB Manager
with a database name of "TestDB567" before attempting to use the sample app.
>>

I don't know what is going on, but I can't hold off the 1.01 release for
this so it will have to wait at least another week for a fix.  EDB works
fine with a normal TDBGrid, so they must be trying to rely on some specific
behavior that they shouldn't be relying on.

I'll let you know what I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim:

By all means, please go ahead with the update first.  I'll look forward to
hearing what you learn about this later on.

As an aside, I purchased DBISAM with an upgrade path to EDB in November
based primarily upon the good things people had to say about ElevateSoft and
upon the excellent support I've seen in these newsgroups.  I just wanted to
say "thanks" for not letting me down; your support here is second to none.

Greg

Greg

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:EEB5DE18-440C-4A60-928F-8BDFD85EE2FD@news.elevatesoft.com...
> Greg,
>
> << I've encountered a problem using cxGrid from DevExpress in which it
> appears the selected row in the grid might not be accurately represented
> in the underlying dataset.  I encountered the issue using a TEDBQuery
> component
> with the grid.  I first thought it might be an issue with the TcxGrid but
> tried to replicate the issue with an ADOCennection/ADOQuery and an Access
> table and couldn't reproduce it that way.  Hence, my post here.
>
> I've posted a sample project to the binaries newsgroup to demonstrate what
> is happening (see Test567).  Realizing that you may not have the
> DevExpress component available, I included an EXE within the project
> directory (Test567.exe).  There is also a folder called "edb" which
> contains a test edb database used by the project.  It should be configured
> in EDB Manager with a database name of "TestDB567" before attempting to
> use the sample app.
> >>
>
> I don't know what is going on, but I can't hold off the 1.01 release for
> this so it will have to wait at least another week for a fix.  EDB works
> fine with a normal TDBGrid, so they must be trying to rely on some
> specific behavior that they shouldn't be relying on.
>
> I'll let you know what I find out.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Greg,

<< By all means, please go ahead with the update first.  I'll look forward
to hearing what you learn about this later on. >>

At first glance it looks like they're copying around row buffers and
bookmarks in a way that isn't compatible with EDB.  EDB doesn't use PChars,
so it has to embed row objects in the row buffers used by the TDataSet
architecture, and this type of setup is not compatible with copying the
buffers around like that.  I'll have to see what I can do as far as
"jockeying" around the situation.

<< As an aside, I purchased DBISAM with an upgrade path to EDB in November
based primarily upon the good things people had to say about ElevateSoft and
upon the excellent support I've seen in these newsgroups.  I just wanted to
say "thanks" for not letting me down; your support here is second to none.
>>

Thanks for the kind words.  We're certainly glad to have you as a customer.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim:

Thanks for putting out the 1.01 update -- I just installed it.

I tried using a TEDBTable component instead of a TEDBQuery component.  I
found that the row offsets aren't occurring with the TEDBTable ... just the
TEDBQuery components.  ... for whatever that might be worth to you.

Greg

Greg,

<< I tried using a TEDBTable component instead of a TEDBQuery component.  I
found that the row offsets aren't occurring with the TEDBTable ... just the
TEDBQuery components.  ... for whatever that might be worth to you. >>

Most likely just a coincidence.   I've fixed the issue, and the next 1.01
Build 2 will fix the problem for you for good.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks, Tim.  Looking forward to it.

Greg