Again trying to change an EWB2 app to EWB3 and having difficulties getting things that used to work not now working in EWB3

I have a form with a Tgrid bound to a EDB dataset I also have an edit box which is used to enter text that is used to search the dataset  This works as expected when searching on the complete value of the field  but when attempting to find the Nearest match eg I enter 'BL' when seasrching for 'BLAK' I get the  the error 'Row index -1 out of bounds'

Here is my code

   tbCustomerLookup.Columns['AccCustID'].SortDirection:=sdNone;
   tbCustomerLookup.Columns['Account'].SortDirection:=sdAscending;
   tbCustomerLookup.SortCaseInsensitive:=True;
   tbCustomerLookup.sort;
   tbCustomerLookup.Find(['Account'],[edSearchCustomer.text],True,True,False);
   edsearchcustomer.text := '';

This has no been fixed in 3.02

I am getting this error in 3.01 Build 4.

   Codes.SortCaseInsensitive := True;
   Codes.Columns['Code'].SortDirection:=sdAscending;
   Codes.Sort;

I load the Codes dataset and sort.  All is fine.  If I reload after the Sort I get the Row indesx -1 out of bounds error.

Walter

This index error also happens if you load a dataset and attach it to a grid.  Click on a Grid Column to sort.  Now reload the dataset and the error will happen.

I expect the grid is probably calling the dataset.sort ....

Just thought I would pass this along.

Walter

This code works in EWB2 but not EWB3  (from a button click) Same error when table attached to grid

   tbCustomerLookup.Columns['AccCustID'].SortDirection:=sdNone;
   tbCustomerLookup.Columns['Account'].SortDirection:=sdAscending;
   tbCustomerLookup.SortCaseInsensitive:=True;
   tbCustomerLookup.sort;
   tbCustomerLookup.Find(['Account'],[edSearchCustomer.text],True,True,False);

Just to be clear the Findnearest bug is fixed   It is when I try to change the Sort direction from one coluimn to the other that the error occurs

For me - just alling Sort then reloading the dataset (after the sort)  Database.LoadRows(XXX,false) causes the error - whether you called Dataset.sort or click a column on a grid to sort.

Hopefully yours and mine are the same error for Tim to fix.  I did submit an incident report so I know he is working toward a resolution.

Walter