>>>
>>>So, if you have a client that comes to you and says "Great program you wrote for me. Now I want it on the web", what do you do? VFP is not the answer here.
>>
>>I just need clarification here. Why is VFP not the answer?
>
>How you going to provide a UI? ActiveDocs are not a viable solution.

No, they aren't. In fact, they aren't supported by Netscape, are they? If they aren't, IMO, they are never a viable solution. I don't see myself telling clients/associates what browser they have to use.

My opinion is this: There is a system in place with VFP code that works. I can recode the data processing and calculations in something else, or I can build a VFP ActiveX server and use that. This is what I prefer. When the time for modification comes, I have to modify code in one place for the Windows-based solution and the Web-based solution. I basically work in one system that has a lot invested in the database design and the calculations to work with that specific database design. So, in my situation, I would push for re-using code as much as possible. Which would mean making ActiveX servers. To code and test two sets of calculation just doesn't make sense in my situation.

I also have to note that I haven't made any Web application. I've read some articles, and I've built VFP DLLs, but I've not build even a tiny Web application. So maybe I am mis-informed.

I thought VFP 6.0's FoxISAPI and other tools, you can build HTML code with VFP ActiveX servers that can be used in Web pages. Is this not correct?

Also, lets be clear. I am not making general statements that re-writing code is never an option. I am just saying that I am in a situation where that would be the very last resort.


Take care,
Joe