James,
VFP mtdlls called from ASP/ASP.NET is something to consider for web apps and my recommendation. You get to keep pure VFP code and can do a little ASP/ASP.NET and C#. Check out www.dotcomsolution.com/dev for more info and demos.
Also, check out Mike Stewart's (Microsoft) comment about the performance of VFP mtdlls called from ASP in message # 627606
>Thanks Larry.
>
>ColdFusion is one of the products I was looking at. I also looked some at ASP but that looked like it would be hard to manage in a large project. Does the data access part of ColdFusion have to be coded in the page like ASP?
>
>
>>>Hi All
>>>
>>>I have a big web project (actually two of them) coming up and I am trying to make a decision on what tool I should be using. The question here is if there is a good reason to stay with VFP or not. The one big plus to VFP is it is a language that I know and understand. Are there any others? I have played a little with WWC and is seems to work ok. This project will require a lot of database work and, eventually, will be processing an excess of 1 million credit card transactions a year. I am looking for thoughts, opinions from anyone that have been there, done that before.
>>>
>>>Thanks.
>>
>>Take a look at Macromedia ColdFusion. You can download a trial version at the macromedia web site. I've been impressed with this as a very quick way to get things up and running, with terrific error-checking. It integrates well with Dreamweaver, and also has its own GUI, ColdFusion Studio, which is very fine.
>>CF has a relatively short learning curve.
>>
>>Of course, you can continue using VFP for all of the database back-end work, and you still use .dbf files if you want.
>>
>>One thing CF is not good for is highly interactive systems, like bulletin board systems. There seems to be a speed penalty there. Imagine the UT 10 times slower, and that might give you an idea. For anything other than that, I highly recommend it as a candidate.