John,

In general, you shouldn't be using views without parameters or some other filter condition in the WHERE clause. The only exception would be very small tables like lookup tables. Also, when you update a view you should be using key fields that are indexed in the underlying table. When you use TABLEUPDATE() on a view, VFP just generates a SQL UPDATE statement then uses it to update the table.

>Are views as fast as using tables? I have noticed that views try to load all data within a table prior to becoming available to the program (unless you have some sort of filter). This does not seem to be the case when opening a table to view (see) browse. It would appear that directly opening/using tables is better/faster. I've also noted that using tableupdate(1) using a view (using a table without indexes) takes much longer to save than the same save using the tables directly.
>
>Maybe there is somesort of parameter that I'm missing that limits the way views get records? Or some other parameter that will cause views to save faster.
>
>John