Access was the default provider for version 2.0. It was removed in 3.0 and sql server is the default provider. Other providers are available so you can use them. No big deal, since you can get MSDE or SQL Express for free.

.Net has access to the memberbership and personalization information with controls out of the box, you'd have to write the same stuff in VFP. Does your product allow multiple sites from the same code base and tables? Can you apply skins, as well as different skins to every page? I think not, why try to reinvent the wheel?



>Did they ever hear of an install program? The latest DNN version wouldn't run after compilation because it required a SQL Server setup. DNN version 2 setup ran successfully I think because it uses an Access mdb instead. My opinion right now is that ActiveVFP could do a better job with this. Is there anything unique to .NET that makes it good for doing such a project??