SQL Server is the way to go. It is at least as fast as VFP. You just need to rethink how you use data. SQL Server is also more scalable and secure. It also works better with .NET than ADO.

Rewriting an app is a big undertaking. There are techniques to use that make it easier. Look at the book "Brownfield Development in .NET"

>It sounds like you are sure that most tthings should be in the document, tick that.
>
>I was looking for the contents of adovfp.h in the code listing on P9 of your document.
>Not to worry though, as I managed to dowload adovfp.h etc from the KB article that you mentioned on P9 of your article.
>
>Thanks anyway.
>
>FYI - we are extending a large desktop VFP app by doing a whole lot of new stuff using Winforms and the Interop toolkit.
>Down the line we will redo all the VFP based UI in .Net, the data access layer will very likely remain VFP as it is still the quickest car on the lot in our experience,
>In your experience are we on the right track here ?