>Greg,
>
>You can index a RV in the standard fashion - index on myexpression tag myexp .
>
>Is the purpose to display data in different ways or to allow browsing/editing of data in different orders? The biggest benefit from a RV is the injection-proof automatic updates. If you're only displaying the data or editing data one row at a time in a separate form, you might consider SPT for the list and a separate RV to pull individual records for edits. That will make it easier to transfer to a web app as well, should that ever be contemplated in future.
>
>HTH

The application is a point-of-sales application. And a few of our clients are quickly near the 2gig table size limits. My purposed convert them SQL server and ask me to investigate and come up with some solutions. The RV solution was my first idea as a means to resolve the problem while we go through the code and rewite to a better solution. Also, he would like to continue have the application use FoxPro table for the smaller clients. The RV seem like to easies solution. For the small client we would provide a DBC and the tables. But for the clients, we provide a DBC of RV to SQL Server. If this solution becomes a problem, we can always SQL Server Express for the small clients.