Nadya:

>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...

Reset Filter and Order at the end of your Save method (if successful).
If you to keep the filter and pre-fill some fields, I recommend that you make the controls associated with these fields ReadOnly or, at the very least, remove them from the TabOrder.

What you are trying is not easy because you also have to give enough visual clues to the user that a filter is on/off and any additional record will be limited to the filter condition.

Good luck,
Daniel