Visual FoxPro developers from around the world gathered at Visual FoxPro DevCon 2002 in Fort Lauderdale, Florida for the official launch of Microsoft Visual FoxPro 8 (formerly 'Toledo'). Each attendee received a CD of the VFP 8. Microsoft Visual FoxPro group product manager Ricardo Wenger, Visual FoxPro product manager Ken Levy, and other Microsoft team members introduced many of the compelling new features in the keynote address.
Oct 10, 2012 Well, I am not an expert on XML, the only really good source of XML handling in VFP is wwXML from West-Wind, if you want something foxpro specific, but I don't see how it includes parsing and validating XML and pointing out and describing errors.
Microsoft Visual FoxPro 8 is based largely on developer feedback. VFP 8 provides a better smart client and new ways of working with data. It's focused on increasing developer productivity, and is more 'discoverable' (i.e., easier to use and figure out) than previous versions. The Fox team also proudly announced that VFP 8 is currently more stable than VFP 7 SP1, and that it's the most exciting release since VFP 3.
The user interface in the new version is similar to Windows XP. It also integrates well with Visual Studio .NET. For example, a form created in Visual Studio .NET works with FoxPro data. VFP 8 also extends interoperability with SQL Server.
Microsoft also provided a brief glimpse of the next version, Visual FoxPro 9 (Europa). It's still in the early stages, but one potential feature demonstrated by Calvin is a new way of resizing forms.
News source: Bink Windows XP
View: the full story
1. Introduction
Visual FoxPro requires certain versions of system components to be installed prior to installing client components.
2. Required Baseline Components
- Setup Runtime Files
- Microsoft Data Access Components v2.7
- Windows Installer 2.0
- Microsoft SOAP Toolkit 3.0
3. Known Installation Issues
3.1. Hung Installation
If individual components hang during installation, setup may be unable to detect this. Use CTRL+ALT+DELETE to manually shutdown the setup.exe task. Note, installation of larger components can take as long as 20 minutes on slower machines or when installed over a network.
4. Additional Issues
4.1. Diagnosing failures in System Component setup
You must install system component updates before proceeding with Visual FoxPro setup. If the installer reports failures for a component at the end of setup, you can run the individual setup for the failed component to see the specific errors and diagnose problems. The location of the components on the Visual FoxPro CD is as follows within the WCU folder:
Component | Location on Visual FoxPro CD (within WCU folder) |
Setup Runtime Files | bootstrap.msi |
Microsoft Data Access Components v2.7 | MDAC27mdac_typ.exe |
Microsoft SOAP Toolkit 3.0 | SOAP3soapsdk.msi |
Windows Installer 2.0 | windowsinstallerwinntinstmsiw.exe |
If setup continues to report failures, even though the individual setups succeed, you can bypass the system component updates. Please note however, this is only advised if all required components are installed. Visual FoxPro will not function properly without these components.
To bypass Prerequisites setup |
---|
|
4.2. Uninstalling Baseline Components
Uninstalling Visual FoxPro does not uninstall components installed by Prerequisites setup. For components that offer individual uninstall, use the Add/Remove Programs in the Control Panel.