>Yes that exactly how my code looks. I am trying to retrieve one record with about 10 fields in the view definition. I have an index based on trimming the id - could that be a problem.

That is your problem. VFP used fixed length keys. Period. TRIMming the key will not change this...in fact, it will make things worse. Also, Rushmore looks for an *exact* match for the index. See the KB article on my web site for more information.

>Potentially I will be pulling in even more fields from related tables and feel that if this is a problem at this level maybe I should not be using local views.

Local views are not the problem.

>This is my first experience using view and need some advice on when it is appropriate to be using views.

IMO, unless you have a multi-tiered application, which I prefer, you should always use views.

>My application is using native FoxPro tables. This is an telephone application in which users must be able to access the information very fast. My recordset is about 121,000 records and it takes about 8 tenth of second on my 600 mhz machine to requery the view - however user don't have as powerful machine as I do. Also all my testing has been done on my local machine what can I expect when I put this on the network.

The network will be slower. Network speed can vary depending on traffic, topology, etc. We have several hundred users hitting our server. The application uses views and we don't have problems.

>
>Thanks