Hi,

I don't really know enough at this time to make that decision. Given our situation, the program will never be widely distributed. Only a small number of components would ever need to be used off-site. Based on what I do know, HTLM/XML/ASP does not have the UI capabilities of regular Windows sceens that would be desired. EHC plans are co-dependent on input forms as they have to be entered into forms, and these forms have to allow for all the plan options.

Anyways, I am not saying that there is not a situation where a Web interface-based solution is not the best. In fact, I think there are many situations where this solution is the very best. I am just saying not EVERY solution.

Take care,
Joe

>I see your point and agree. I am speaking mainly of user interfaces.
>And I agree that rewriting an application for the sake of having
>a internet\intranet presense is silly. And writing an
>single user or simple type of application (some one else
>brought this up) using a web interface is not the best use
>of resources.
>
>But if you were writing this application from scratch and the
>program was widely distributed, using a web interface that can
>easily be accessed from anywhere with no installation problems,
>and having your highly flexible EHC plans independant of the
>input forms, would you choose to do it that way?
>
>
>>Gene, there are companies out here that have systems that have been developed over many years. This is not something that you convert just for the sake of speculation of the discontinuation of a product.
>>
>>Let me give you an example of where VFP would be the solution of choice for a WWW site: We have a system that does, among many other things, claims adjudication for extended health care claims. The calculations are rather involved given the highly flexible EHC plans that are available. This code is in place and used virtually every business day. Now, say we want to allow the employees of clients to connect via the WWW and enter a claim for a pre-determination to see what would be paid if they incurred an expense for whatever type of benefit (this applies to dental coverage also). Well, we can take existing VFP code and compile to a DLL and use that in our WWW page. Or, we can try to re-write the adjudication method in another language. Did I mention that group insurance is a fast-changing business with many plan options being added regularly? This means changes to the adjudication calcs. By not using VFP for the WWW page, we would essentially double our maintenance of the
>>adjudication portion of the program. Well, probably more than double, since the other stuff would be written in non-VFP ;~)
>>
>>Do you see my point?