Well I have to be honest, performance is not the ONLY reason that I would lilke to convert the APP to use SQL Server. This is an application that I resell. It was purchased from someone else that paid consultants to design and develop the app. It would look good ont he sales side to be able to say the app was developed with SQL Server as none of the compitition is. I guess what I am really looking for is some sort of list of data related operations in FoxPro and what will and will not work with SQL. For example, do the SEEK and SCAN commands still work? Should I be binding all my combo boxes to cursors? That sort of thing. Where it become appropriate, I will redesign the table, indexes, and the way the data is retrieved. But for the most part, I just need a starting point - and I think that point it to identify what commands work and do not work under SQL. So far I am in the middle of re-designing the login system. I was amazed how many tables were accessed before the login screen. The login screen was where I wanted the user to select the SQL Server, Database, and username/password combo.

>>Thank you for the well thought out answer. Many times people will tell you to just go buy a book. I am not convinced that adding a framework to a poorly designed application is the way to go, but I will certainly take a look at that.
>
>I completely agree that adding a framework to a poorly designed app is not the way to go. I would also suggest that putting a lot of time and effort into doing any kind of conversion on a poorly designed app is not the way to go.
>
>The advantage of a framework is that it facilitates what really needs to be done - redesigning a poorly designed app with a good RAD tool so as to make the conversion worth the time and effort.
>
>Short of that, converting a badly designed app to a SQL server backend is not going to make it a better designed app.
>
>If any kind of redesign is not in the cards and you just want to tweak performance, just fiddle with indexes, config files, get the fastest network hardware you can and live with the result. You'll never get the kind of performance that comes with good design and parameterized views, whatever the backend.