David,

I agree that ASP.NET is huge for web development but I think using MSDE, MS SQL Server, or even MySQL is better for the database backend. Particularly if you are using a virtual/shared server.

Shared servers (where you pay $15/mo or whatever) are really a pain with VFP because you can't modify structures easily (no terminal server access) and IIS immediately locks up the tables so you can't pack or reindex. With a dedicated server it's not that big a deal to shut the services down to get exclusive access. Plus you can put VFP on the server to help with the inevitable maintenance. With a shared server you can't shut down the services and you certainly can't install VFP on the server.

Unless there is legacy data already in VFP or a strong motivation to go with VFP as the database, I think there are much better choices that are easier to maintain.

Greg


>Bob,
>
>>...I do not have anything against .NET, hopefully it will be a stable platform for design work for a few years into the future, but it offers me little.
>
>Just a different angle to consider for a moment...
>
>One thing that .NET can give you is easy development of web pages that talk to your Fox tables and extend your Fox apps onto the web. Sure, there are still several good Fox-based products that can do that too, but ASP.NET really is a very good platform with many, many hosting options at reasonable cost.
>
>You don't have to embrace .NET completely for all development, in other words, to benefit greatly from ASP.NET.