A Place To List Why We Use Fox
- Fully Object Oriented.
- Integrated tools for forms, menus, reports, debug, help, installation.
- Native metadata for all VFP's structures allows complete manual/programmatic editing of metadata which is priceless for application-wide changes that might otherwise take significantly longer to perform manually.
- Excellent front-end for back-end data stores.
- VFP is also extremely inter-operative with a wide variety of both legacy and modern data formats.
- Many development / run paradigms (EXE's, compile on the fly FXP's, COM DLL's, EXECSCRIPT, etc...).
- The Command Window arguably cannot be beat for interactive data management.
- The Command Window is useful at design time and in suspended run time.
- VFP is layer-agnostic.
- It makes a great front-end for back-end databases in 2-tier designs because of its connectivity and data manipulation abilities.
- It makes excellent middleware components in 3-tier designs for the same reasons.
- In all cases it makes for excellent and notably un-bloated client applications, again for mostly the same reasons as above.
- VFP can also be used to create monolithic applications.
- Data handling capability is encapsulated
- Database commands are integrated in the language.
- Data handling commands are integrated in the language, which benefits applications that manipulate data. For example, the downstream quering and processing of result set cursors is an absolute snap in VFP.
- No notable weaknesses. VFP is excellent for manipulating numeric, string, text, binary, XML....
- Good COM story.
- Good XML story.
- Reasonable .NET interoperability story. Expect this to get better going forward since VFP is from Microsoft.
- Good backwards-compatibility story. Legacy Fox systems have many paths forward.
- Flexible syntax and execution.
- Easily localized.
- Possibility to subclass ActiveX components (OCX).
- The ability to compile code at runtime via execscript()/&,
- Visual class designer (visual subclassing).
- Many of the VFP IDE tools are open, extensible, and table based, etc. VFP includes the source code to the Xbase components.
- Internationally available (Spanish, German, French IDE) due to licencing of Microsoft Resource Localization Toolkit.
Notable Development Capabilities
- Integrated development environment
- Powerful local data engine
- Hybrid database access (mixed record- or set-oriented)
- Hybrid programming model (mixed procedural and object-oriented)
- Explicit physical containership-model for most visual and some non visual base classes, instead of simple-frame as found in many other MS products, notably VB, or none at all as in C++.
- Interactive (and scriptable) design tools
- Small runtime.
- No runtime fee for application distribution.
- No runtime fee for the database engine.
- No runtime fee for the report writer (which has been significantly enhanced in VFP 9. See Europa Features).
The VFP Revenue Model, and specifically the VFP Revenue Model Problems, is probably the most important reason, among others (see Other Issues below), why Microsoft doesn't push VFP in any real marketing sense. Hence the skepticism found in IT towards VFP: It's not, and never is, on the Microsoft Band Wagon.
- Typically runs fine on old boxes, with old OSes, and you typically won't ever need a cutting edge OS upgrade or service pack upgrade to run a next version, nor will a future service pack or security patch play havoc with your Fox applications.
- Stable, mature, complete development environment.
- Stable, mature supporting frameworks for UI, middleware, data, web.
- Well established and recognized best practices.
- Low rate of change.
- On balance, well directed evolutionary change.
- XCopy deployment: Copy your Exe and the RT-DLL into your Directory, that's all you need. (Works even with most ActiveX; nothing to register)
Developer Community Issues
- Dynamic and experienced developer community, wired since the early 1990's.
- Unparalleled peer-support for those who chose to be connected.
- International developer community aspects.
- Excellent grapevine for locating and evaluating potential developers.
- Not on Microsoft Bandwagons. Here's why:
Although Microsoft doesn't state it quite so bluntly, Visual FoxPro's foremost competitors are Visual Studio, Microsoft Access and SQL Server. That explains in large part why the Redmond software vendor isn't jumping through hoops for Visual FoxPro. -- Microsoft Watch, Thursday, June 03, 2004
- See Microsoft Product Life Cycle Dates . At Tech Ed 2004, Microsoft announced a standard 10-year lifecycle horizon (5 years Mainstream and 5 years Extended) for all its business and developer products, which at this time extends VFP support from MS into the year 2014 at minimum. Prior to this VFP 8 had a support horizon of 2010.
- MS working on VFP 9. See Europa Features and Visual FoxPro Version Feature Concordance.
- US military critically depends on VFP.
- Not built into Windows.
- Runs on a wide variety of legacy Windows clients.
- Minimal, nearly zero reliance on the windows registry.
- Runs on Linux with WINE (But, for the moment, this pre-supposes Linux skills in excess of the Windows skills required to install and run under Windows.)
- Fox team, as a unit, is notably stable.
- Fox-savvy people are at every level at Microsoft (Rudder, Lazar, Green, Griver, Hsia, Goley, Levy, et al.)
If we're talking about a Web Application, then many of the headaches normally associated with *some* legacy FoxPro experiences, namely
... just don't exist, and as go your web servers (physical security, network security, performance) so goes Visual FoxPro.
- Client-side installations.
- Network shares required.
- Volume of network traffic.
- Tables accessible by other applications.
The recently added TCO (total Cost of Ownership) points moved, for now, to Talk : Visual FoxPro Bullet Points -- Steven Black
Category VFP Marketing Category 3 Star Topics
( Topic last updated: 2010.12.26 08:46:40 PM )