Hi!

SQL Server is not a VFP. There is a great difference - SQL Server designed to manage a huge amount of the queries, and is not designed to process the data. Thus, there are little of the data processing commands. There are no such term as 'Alias' and 'Current record'. You can use a cursor, but for records scanning only, you cannot search and cannot locate. VFP is very different.

All this cause VFP application for SQL Server look and function diffrent. The difference is so great that sometims the interface of the application should be re-worked for optimal performance (the best approach for SQL Serevr applications is do not work with data sets that contain more than 1000 records). Usualy, such application forms start from the search page, where user enter conditions of which records he want to see and than work with thsese records.

You still can use VFP commands and indexes, however, with the local data sets only after you received data by a query or by the view from the SQL Server. Yo can index a result set on the fly usingINDEX VFP command, than use it to sort the information in a grid, organize quick search etc. You cannot use SQl Server this way. You can only download data from SQl Server and send updates there, as well as SQL commands.

HTH.


>Hi all,
>I create an index of a table in SQL server.
>can I call this index to use in my VFP program?
>and can I use the "Seek" command to search records?
>If so, how to do this when I CREATE SQL VIEW?
>I have tried to index a remote view, but I found
>all records will return from SQL server to
>my workstation. This will increase the network
>traffic that I don't want.
>The property "Fetch" how many records at a time
>is useful, but the view only allow me to
>"Locate" a record. How to "Seek" a record ?
>Becuase I found this is the fastest.