Terry,

I finally got a chance to look at this, and it appears to be an issue with
DevExpress' TreeView.  It works okay if you set the active index to the GUID
column that you're using, but it seems to have a problem when using the
table in its natural order.  The treeview simply isn't positioning itself on
the proper row prior to the edit, so when it goes to edit the row, EDB says
"whoa, you're trying to edit the wrong row".

An interesting illustration of this is to plop a TDBGrid down on the same
form along with the TreeView and hook the grid up to the same datasource.
The problem will go away because the grid will always properly position the
row prior to the edit.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> I finally got a chance to look at this, and it appears to be an issue with
> DevExpress' TreeView.  It works okay if you set the active index to the
> GUID column that you're using, but it seems to have a problem when using
> the table in its natural order.

I was aware that setting the active index resolved the issue for the
TEDBTable object.  But as the TEDBQuery object doesn't have this property,
this isn't an option for a query object.

> An interesting illustration of this is to plop a TDBGrid down on the same
> form along with the TreeView and hook the grid up to the same datasource.
> The problem will go away because the grid will always properly position
> the row prior to the edit.

Thanks for the workaround.  This will at least let me use the component and
keep moving forward on the project.

--

---------------------------------------
 Terry Swiers
 Millennium Software, LLC
 http://www.1000years.com
 http://www.atrex.com

 Atrex Inventory Control/POS -
    Big business features without spending big business bucks!

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

Terry,

<< I was aware that setting the active index resolved the issue for the
TEDBTable object.  But as the TEDBQuery object doesn't have this property,
this isn't an option for a query object. >>

Result sets default to using the primary key of the first table in the query
as the sort order, or the GROUP BY or ORDER BY, if specified.  Just make
sure that one of these two situations exist, and it will be okay.

--
Tim Young
Elevate Software
www.elevatesoft.com