>OK. I don't understand how I missed this. This obviously just went right over my head. I knew my views were not always optimized. I accepted that it would be slower but I guess the part I missed is I had no idea how much slower.
>
>So I guess that is the answer I have been seeking. VFP can be horribly slow if your views are not optimized and you have a good bit of data and you will have multiple users. Hopefully this will serve as help to keep someone else from having this issue.
>
>I would appreciate your input.
>
>As I stated earlier I am trying to move to TSQL. I am worried that doing so may not alleviate this issue. Would it be true to say that I should optimize my views (meaning make them fast whatever that consists of) BEFORE switching to TSQL? I am NOT referring to making them faster so my users have a better experience until I get to TSQL. I mean is this something I had better do because TSQL will not work much better unless I do so.
>
>Thanks,
>John

You're not the only one that missed how Rushmore works. Many only find out as their app's data reaches a certain size. SQL Server's optimizer started out as Rushmore. It has some similarities, but they continued to evolve it to the point where it can do lots more.

There is another major difference. SQL Server has direct access to the data. It is like running VFP on your local PC. There is no shared access.