Hi Mike,

Actually I found this problem with the index, which was filtered, e.g. has not empty Filter expression, what's why I talk about set order to. But the same applies to filter as well. Now the problem is how to handle this situation. We can put a check in our base classes, if the current order has filter or if filter is set on, and if so, turn it off while appending a record. The second question is where and when should we restore the current status, e.g. put index or filter back on, because the processes of appending and saving a record are separate. Also there are some situations, where we don't want to turn off the current filter, but pre-fill fields to satisfy filter condition instead. So, from my POV, we should add a new logical property to our form, which tells us, what we have to do...


>Hi Nadya
>
>If you have a filter active when you append blank, the new record likely doesn't meet the filter condition. Any record pointer movement will make VFP evaluate the current (new) record against the filter. When VFP finds the current record doesn't meet the expression, it moves to the next record that does meet the condition. SET ORDER has nothing to do with this. You will have to reset the filter, not the order.
>
>HTH
>
>Mike