Hi Michelle,

>Heh... Actually, I think John Kozial(sp?) has the quickest at around 20 seconds.

John Koziol :) This word 'koziol' or 'kozel' means (how to say?) - male goat in Russian :) and as John explained to me in one thread, he has Polish ancessors (?sp)... In Poland the meanning of this word is different and much more respectful, if I remember correctly, it means goats owner :)

Anyway, enough about John and let's talk about this particular problem.

>
>I guess in your case it would be better to temporarily set the filter off.

It's a index filtered, not the Filter. So I'll take it to SET ORDER To.

It's really not an issue for me because I don't write apps. All I do is modify SBT and their method of doing anything bears no resemblance to anything a sane programmer would do. :)
>
>Sorry I wasn't any more help.
>
>Michelle

Thanks anyway.

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