Hello Jorge

I didn't take your comment as a insult or to harsh, the only reason I don't use views is it feels like I have a lack of control and I don't know them very well. I agree a filter can be very slow (I learned it the hard way). I like the control I have with a locally stored table and the gathering of data in the beginning and the update at the end are the only places where the code could go slow and again with views I just don't what to expect.



>To Stephen:
>
>Excuse me if it sounded harsh, I didn't mean it to go through that way, but what you describe, while clever, is something that VFP does natively through updatable views.
>
>To Steven:
>
>I haven't used views in a while, but the changes to your code should be minor, the most important one is that you'll need to requery your table manually if it's a child in a one to many relation.
>
>You could also just create a compound index and use a relation so you don't have to create an index every time.
>
>I'm not a big fan of filters because they seem to run slow over a network, sometimes excessively slow, I suppose it all depends on your indexes (indices?)
>
>HTH
>
>>I have never used a view, so how am I going to tell anyone else how to use >one
>>
>>>Why not just use a view?
>>>
>>>>Well Steven I would say to do a work around and not a filter