Tim

I don't know if this is your's or TMS's so I'm posting both, but I suspect them more than you. I updated my lookup stuff for TMS and ElevateDB. I first went for the look and left DBISAM in place and got things working. I've now upgraded to ElevateDB and I'm having problems.

With DBISAM I could close the query, alter the ORDER BY clause and re-execute - no problem. With ElevateDB I'm having to set the datasource.dataset := nil (just setting the datasource property of the grid to nil doesn;t work).

Is there anything you've done between a TDBISAMQuery and a TEDBQuery that could cause the problems?


Roy Lambert

Roy,

<< With DBISAM I could close the query, alter the ORDER BY clause and
re-execute - no problem. With ElevateDB I'm having to set the
datasource.dataset := nil (just setting the datasource property of the grid
to nil doesn;t work). >>

You never mentioned the important part - what happens if you don't set the
DataSource propety to nil ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

This is the post I sent to TMS

I have a grid linked to a query component. The actual table and fields can vary so the columns for the grid are programmatically created. Column 0 is set up as a checkbox. I have an OnCanSort event. If I click the title bar then the order clause for the query is changed appropriately depending on the column and the query rerun. It works great UNTIL I click on a row in the grid and then click on a title cell. In those circumstances I get EInvalidGridOperation 'Grid index out of range'.


Roy Lambert

Roy,

<< I have a grid linked to a query component. The actual table and fields
can vary so the columns for the grid are programmatically created. Column 0
is set up as a checkbox. I have an OnCanSort event. If I click the title bar
then the order clause for the query is changed appropriately depending on
the column and the query rerun. It works great UNTIL I click on a row in the
grid and then click on a title cell. In those circumstances I get
EInvalidGridOperation 'Grid index out of range'. >>

It could be this issue also:

http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&category=edb&release=1.02&type=f&incident=2325

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Possible - I'll have to wait for 1.03 to find out HINT HINT

Roy Lambert