I finished surfing a simple Install Shield curve. I note that to deploy a VFP EXE, a C++ Runtime is required.

So, in a sense, your prospect would be getting the magic of VFP and the comfort of knowing that C++ services some components of the project.

THe text file functions could probably be handled much better in a VFP cursor.



>[snip]
>>Here's what Microsoft says when comparing the 2 development environments:
>>"Q. Why would I build a component in Visual FoxPro when I can build the same component in Microsoft Visual Basic or Microsoft Visual C++?
>>A. Visual FoxPro components are extremely fast, thanks to the data-centric language of Visual FoxPro and its ability to quickly retrieve and manipulate data. Further, Visual FoxPro can build character strings very swiftly. A Visual FoxPro component that works with data and returns HTML will, therefore, be very fast.
>
>So, I guess one might state that the VFP string manipulation functions are very closely tied to the C++ string manipulation functions?!
>
>But how about the low-level file functions? It is my hunch that they too are very closely tied to the low-level functions in C++.
>
>[snip]