Can you explain further what you mean by MSDE? Development environment? The software is sold all over the world to potentially anyone with any kind of pc. We only specify that they have to have Windows of some flavor and 32 MB RAM, 10MB disk space free. I'd like to minimize the amount of code I write so it can ideally be transported to any of the platforms.

>Is there a reason you can't use MSDE on the local installs?
>
>
>
>>I have a VFP6 app currently sold on cds that runs only on individual pc - if they purchase an individual license, they also have to have the cd in the drive when the program is run. We want to move this app to run it under several different environments with the least amount of environment specific code. Ultimately, it will:
>>
>>1. Run from a web server (virtual, not co-lo) so people can run the program on the Internet
>>2. Continue distribution of the app on cd for use on single pcs of any type (win95, me, 2k, nt, xp, etc...)
>>3. Allow the app to install from cd to run on an intranet
>>4. Allow the app to install from cd to run from a server accessed from individual workstations
>>
>>I looked into WebConnect but since we are not co-locating, that limits it to a few web hosting companies - none of which are near here.
>>
>>My next thought was VB.NET, ASP.NET, and SQL Server. Well, that will work on the internet but obviously sql server isn't the choice for cd installations.
>>I'm wondering if the best idea is to develop in ASP.NET with VB.NET code but use ADO.NET to access VFP data with the OLEDb provider. I would use VFP7 since the runtime will work on any version of Windows since WIn95, I believe. The important VFP data is encrypted in the tables so I'm not too concerned about the security aspect. If I can keep the data in VFP and build the forms, code with .NET, can't I then make this transparently portable to the cd version? As long as the user has a browser installed, won't this work? Am I missing a step or 2 or 4...? Any better recommendations?
>>
>>I have to keep in mind that the end user may have any kind of pc with any software, browser or lack thereof on it! It gets very confusing to figure out what "extra" dlls or such have to reside on a pc for the various software to run and also what hardware the user must have and I find it hard to get that info from Microsoft help or other venues.
>>
>>Any comments would really be welcomed.
>>
>>Thanks,
>>
>>Sally