There will probably be a small improvement in network traffic, but not much because the index file must be downloaded in order to build the view.

One of the advantage of using views instead of tables, is that it's easier to move the database to a SQL/Oracle server if the need arise.

>After two years of developing un VFP, I've only used parameterized (?)
>views when I MUST have information from different tables in one single cursor, and have always considered them a performance hit.
>
>Just recently I realized that in a network environment it might be a bigger performance hit to send a whole table through the nw, than just the info a given user needs, for instance, instead of sending the whole catalog, just send the required part number.
>
>But, wouldn't it load the whole table to crate the view in a normal application.
>
>THIS IS THE ACTUAL QUESTION :)
>
>Do I need to develop a client/server application to reduce the network traffic and see a performance improvement.
>
>The thing is I usually consider only how my program performs on my development PC, and brand it as acceptable or non acceptable performance, but how it performs over a network is a whole different story.
>
>thanks in advance for sharing your experience