>I've done some research, and found that there is an SQL Server Development version, which allows a developer to create a fully functional SQL Server application, and later upgrade/migrate it to the enterprise edition of SQL Server. I'm also aware of the SQL Server 2000 Desktop Engine, which comes with VFP, and seems to allow the same flexibility for later migration to a full version of SQL Server.
>
>My questions are the following:
>
>1) Which development edition of SQL Server is most suitable for developing solutions off-site (without access to a client's enterprise or standard edition of SQL Server)? Is SQL Server 2000 Desktop Engine suitable for this?
>
>2) What is involved in upgrading an application (developed with SQL Server Desktop Engine) to a client's full SQL Server system? Is this just a simple process of copying the application's database files/tables on to the client's hard drive/server? Or, is something else involved?

Dave:

It is not difficult at all if you design the application correctly (as a 2-Tier app minimum).
MSDE comes with VFP or you can download from MS. It is the same SQL Server Engine as the latest (SQL Server 2000). It is free and though somewhat limited for production use, it is perfect for local development. If you are not up to date with N-Tier design and/or Client/Server programming there is plenty of good information in the help files and online here inthe UT and in places like the Fox Wiki.

If you designed you app accessing data through views or using SPT, then you are almost there. If your app OTOH is a monolithic exe, accessing tables directly with "Use" and "Replace" then you have a lot of work to do to confert it to C/S.

As for delivery, you cannot "copy" the database files as you would do with a DBC/DBF. But there is an upsizing wizard in VFP and it is also fairly easy to write simple scripts to create the databases/tables/etc in the production SQL Server. This is assuming you have proper access to SQL Server at the site. Just ask the local DBA.

Now, if they are small shops that don't have a DBA and ask you to be the one, you would have to learn a lot more, but then that is not developing a Client/Server app, but a completely different job description, and you should charge accordingly < g >.