>James
>
>>>VFP is a great language for hacking quick solutions, but for industrial strength applications nothing beats a pure OOP language<<
>
>May I observe that Cobol is still used in very many banking and other huge-transaction mission-critical systems? There isn't much OOP about Cobol yet it seems to cope.
>
>Glad to hear you're doing well with dotNET. We did some early work in dotNET and concluded that for the heavy data-munging part, the current version of dotNET is far slower than VFP. It is also visibly slower for opening and massaging Word documents (try it). So we're continuing to trial dotNET for HTTP interfacing but for now the heavy server part will stay in VFP.
>
>Final point: I think it was Machievelli who advised that exchanging something that works for something that theoretically ought to work, is laying the foundation for ruin. Caution is appropriate at the moment IMHO but that is just MHO.
>
>Regards
>
>JR

Thank you for your philosophical observations. VFP was not working. It just didn't fit our funcional requirements anymore, so I implemented something that did. If I find myself in a situation where VFP was the right tool for the job, then I would have no hesitation about using it. Flexibility is the key to success in life...