Hi Nadya,
>
>Regarding the records jumping around on the grid: What about using a temp work table sorted in the desired order with no index as the datasource for the grid or possibly a view with table buffering, which I THINK? would give the same result.
>
>Todd

Todd,

Not sure, I understood your suggestion. I think, I would approach it this way: I would save the current key value. In each record movement I would perform a seek of this saved key in Next/Previous methods. This would do it, I hope...

Hi Nadya,

My suggestions of using a temp file or updatable view as the grid's data source are simply an attempt to remove the index from the editing scenario, then post edits to the indexed base table.

It seems that your idea of saving the current key and using it to reset the record pointer should work and would require less coding that my suggestions.

I use grids occasionally (with combo boxes and row highlighting) for simple data entry, although none of these contained combo box values that fueled the base table's index as your's does. Generally I use grids as 'pick lists' to launch a maintenance form.

Im sure I will be running into this problem in my own project and will let you know if I find anything interesting.

Best Regards,

Todd