Mike,

Thanks a lot for your reply.

>Hi Nadya
>
>Don't create a remote view. Do File New: click View then click New File. You don't need a remote view unless you are using SQL Server or Oracle or Access.

I may try to create a local view.

>>>set filter to MyFilterCondition
>go top
>
>It runs very slowly...<<
>
>There has been a lot of discussion about GO TOP vs LOCATE. The LOCATE command without any clauses is what you should use after setting a filter. GO TOP doesn't optimize. Just add a comment in your code to explain to others why you used LOCATE.

I will try this suggestion first and see, if it increases the speed.

>>>I thought, that view could be more convenient and runs faster, but I haven't much experience with views.
><<
>
>They are much more convenient. In this case, you should create a parameterized view. The second app will open the view (in whatever manner you prefer) and you will pass parameters to the second app for it to pull the records it needs.
>
>Mike

The problem is: one applicaion produces free table or part of database table. Another application should operate on this table and modify some fields (say, add a zipcode and plus4), but only for records, which have StNum>0 and Upper(Street)<>'ZZZ'. Right now I open table in DE, alias it as BldMstr, set filter and then do my operations (Auto and Manual Match). Unfortunately, it works quite slow... I'll see, if LOCATE improves the situation, but I doubt in significant improvement. So, if it doesn't help, I'll try to switch to views. Here I'm afraid it would not fit our framework (it works on tables, not on views)...