Thank you for your input. I used to use views in VFP but since I started using CursorAdapter the views became unnecessary.

>Also worth mentioning a few of the quirks of view - especially in regard to Order by which has made me more than a little crazy
>
>http://blog.sqlauthority.com/2010/08/23/sql-server-order-by-does-not-work-limitation-of-the-views-part-1/
>
>I should also mention for anyone converting VFP local views (i.e. against DBFs) to remote views against SQL :
>
>in VFP you can use another view as one of the member of a local view in the FROM. Can't do that in a remote view. But instead of using a subquery you can create a SQL view and do your join against that. Saved me a lot of work in converting many many local views that had joins against other local views.
>
>
>>Hi,
>
>
>>
>>I have a general newbie question on SQL Server views.
>>
>>When you create a view, does SQL Server automatically maintain records in the view? Example. Say I create a view on records in a table that have value in column STATUS set to 'O' and in column CATEGORY to 'ABC'. Do I understand that whenever the base table (on which the view is created) gets records of STATUS 'O' and CATEGORY 'ABC', these records immediately are in the view? When when you, say, change the STATUS to 'C', the record is removed from the view (automatically) by SQL Server?