Hey Marty! Good to hear from you again. Thanks for the clips from the MSFT site.

As I was hoping everyone was reading in my messages, MSFT is saying exactly the same thing: Use VFP to build COM components.

Those are my plans for future usage of VFP. Not UI. Not data storage.

Well, good to hear from you again. I'm in Hawaii on a programming project. I'm back on the mainland in a few days.

Aloha!
Scott



>Hiya Scott! Here's some text I clipped from the Microsoft VFP FAQ page:
>
>Why would I build a component in Visual FoxPro when I can build the same component in Visual Basic, Visual C++, or Visual J++?
>
>Visual FoxPro components are extremely fast, thanks to the data-centric language of Visual FoxPro and its ability to retrieve and manipulate data very quickly. Further, Visual FoxPro can build character strings very swiftly. A Visual FoxPro component that works with data and returns HTML will therefore typically be very fast.
>
>Visual FoxPro also has object-oriented programming capabilities, including inheritance. This provides a high degree of reuse across applications. A Visual FoxPro developer could create a set of classes that includes the core functionality of a Web database component. That code would not need to be rewritten each time a component was needed in a Web application. The developer could merely create a component that inherits the base functionality and then add to it application-specific code.
>
>Finally, building COM components in Visual FoxPro 6.0 is an excellent way to reuse existing code. Code that is already written and tested can be built into a component, rather than being recreated in another language.
>
>What are Microsoft’s plans for future versions of Visual FoxPro?
>
>Visual FoxPro is an important part of Visual Studio and fully supports the Visual Studio vision of building multitier client/server and Web-based applications. Future versions of Visual Studio will take advantage of enhancements to Windows DNA provided by the Windows NT® operating system version 5.0 and COM+, a significant enhancement to the Component Object Model.
>
>What is Microsoft’s commitment to developers using Visual FoxPro?
>
>Visual FoxPro is an important part of Visual Studio and fully supports Windows Distributed interNet Application (Windows DNA) architecture for creating modern, scalable, multitier business applications that can be delivered over any network. The Visual FoxPro design tools and its object-oriented, data-centric language, fast data engine, and component creation capabilities make it an extremely powerful way for developers to participate in Windows DNA application development.
>
>The hundreds of thousands of developers worldwide using FoxPro have an enormous investment in code and existing applications. Visual FoxPro is the best way for these developers to move to the 32-bit Windows operating system and to take advantage of their existing investments. Visual Studio is the best way for developers to build applications using the Windows DNA framework. That is why Visual FoxPro ships in the Visual Studio box. Microsoft is fully committed to Visual FoxPro and to providing developers with a clear path forward for using it within the Visual Studio family.
>
>How do you position Visual FoxPro in relation to Microsoft Access?
>
>Microsoft Access, the database in Office, is the most broadly used and easiest-to-learn database tool Microsoft sells. If you are new to databases, if you are building applications that take advantage of Microsoft Office, or if you want an interactive product with plenty of convenience, then choose Access. Visual FoxPro is a powerful RAD tool for creating relational database applications. If you are a database developer who builds applications for a living and you want ultimate speed and power, then choose Visual FoxPro.