Hi Michelle,

That's a quickest response, I've ever saw :) I don't think, this is an applicable idea. This is an Add method of our BaseForm, so it would be:
1) tough to implement it
2) not sure, that it's what our users want.

When they hit an Add button, they want to add a new blank record, not necesseraly (? really missed SpellCheck) a new record, which would satisfy filter criteria. Therefore, I think, I'd rather SET ORDER TO and may be reset it back, after this record would be saved (though it would require the new Form property - CurrentTag :().

BTW, how do you handle this problem in your applications (I suppose, you use some sort of framework with navigation buttons, right?)?

>If you have a filter, then a blank record is likely not meeting the criteria of that filter, and therefore not showing up. You could use INSERT INTO instead and pre-fill it with values that match the filter.
>
>Michelle
>
>
>>Hi everyone,
>>
>>Today I noticed this problem: if I have table buffering and I set order to a tag, which has not empty Filter expression, when I hit Add button (Add method - APPEND BLANK), it doesn't show me a new empty record, but picks up the content of current record instead.
>>
>> Therefore, my questions are:
>> 1) Do you notice this behavior before?
>> 2) How does your framework handle this problem?
>>
>> I may think about this possible solution:
>> Before APPEND BLANK check the current index filter expression and if it's not blank SET ORDER TO. But there could by other ways to handle this problem.
>>
>> Thanks in advance.