Hi Jim,

Thank you very much for answering my question.
I have seen you always have a big knowledge of VPF Concepts.
That's good because you can take rigth decisions all the time.

This is my case: I have always worked with VFP tables and relationships and i'm sure they are very fast in order to get records from different tables.

I use VFP as independent programmer because the company where i have my job uses another tool (Unify + Accell/SQL for UNIX).
So i haven't tried all VFP characteristics (Views and remote data), but i love it, and that's why sometimes i ask myself: Did i choose the best method? are there more options ? How do other people do it and so on...

Well, i think it's a matter of time.

Thank you very much, again.

Juan Carlos.



>>Hello Sergey,
>>
>>Yes, i was asking about it.
>>Also, This relationships work faster than views, do you think so?
>>
>>Thanks,
>>Juan Carlos
>
>Juan Carlos,
>
>That depends on what you are doing with the data. A relation takes milliseconds to set, while a view may take longer to get the records. However, once done the view may function quite faster than the relationship while processing those records.
>
>Also, a view can make your code considerably simpler as it deals with a single work area instead of multiple work areas, while a relationship has to deal with the physical storage of the data in multiple tables.
>
>Views are also more easily upsized to working with data that is not stored in VFP tables, while the relationships are limited to only VFP tables.
>
>So, as you can see, there are many issues that influence whether it would be more prudent to use a relationship or a view to process the data besides the time it takes to process one single command (SET RELATION or SELECT).