| Visual Foxpro |
Article Index for Visual |
Website Links For Visual Foxpro |
Information AboutVisual Foxpro |
Visual FoxPro is a data-centric -based and Microsoft has stated that they do not intend to create a Microsoft .NET version. FoxPro originated as a member of the class of languages commonly referred to as "xBase" languages, which have syntax based on the DBase programming language. Other members of the xBase language family include Clipper and Recital . (A history of the early years of xBase can be found in the DBASE entry.) Visual FoxPro, commonly abbreviated as VFP, is tightly integrated with its own relational database engine, which extends FoxPro's xBase capabilities to support SQL query and data manipulation. Unlike most Database Management Systems , Visual FoxPro is a full-featured, Dynamic Programming Language that does not require the use of an additional general-purpose programming environment. It can be used to write not just traditional "fat Client" applications, but also Middleware and Web Application s. RECENT HISTORY In late 2002, some community members demonstrated that Visual FoxPro can run on .http://fox.wikis.com/wc.dll?Wiki~VFPandLinux Rumors suggesting that Microsoft intends to end support for FoxPro have been common since Microsoft's acquisition of the product, despite the product having one of the longest support timeframes for a Microsoft product (extended support until 2015). In March 2007, Microsoft announced "that there will be no VFP 10"http://msdn2.microsoft.com/en-us/vfoxpro/bb308952.aspx, thus making VFP9 (released to manufacturing on December 17 , 2004 ) the last commercial VFP release from Microsoft. The support of Version 9 is ongoing with a service pack that was released December 8 , 2005 . At the time of the end of life announcement, work on the next release codenamed Sedna which was built on top of the VFP9 codebase had already begun. Sedna consisted mainly of Xbase components to support a number of interoperability scenarios with various Microsoft technologies including SQL Server 2005, .NET, WinFX, Windows Vista, and Office 12. Microsoft plans to release these components as community releases via the CodePlex site. On and SP2 Beta was in June 2007 . In December 2005, VFP broke into the top 20 on TIOBE's Programming Community Index for the first time. In March 2007 it is at position 19, making it a "B" language. As of August 7, 2007 it dropped into position 22. On March 13 2007 A Message to the Community Microsoft stated that it will not be releasing its Visual FoxPro development software past version 9.0, Microsoft will continue to support the Visual FoxPro core until 2015 with standard support through January 2010 and extended support through January 2015 via the developer tools life-cycle support plan.http://support.microsoft.com/lifecycle/?p1=7992 Meanwhile, some of the FoxPro-related technology can be seen in other Microsoft products such as SQL Server, Team Foundation Server and various portions of the .Net Framework. In late March 2007 a ) to sign a petition to Microsoft to continue updating Visual FoxPro or release it to the community as Open Source . On April 3, 2007 the movement was noted by the technical press.http://blogs.zdnet.com/microsoft/?p=361 Also on April 3, 2007 Microsoft responded to the petitioner's requests with this statement from Alan Griver :
VERSION INFORMATION Operating system compatibility
Information on Executable Files
CODE SAMPLES Hello World example:
Object loForm = CREATEOBJECT("HiForm")loMine = CREATEOBJECT("MyClass")Data handling
CREATE TABLE randData (iData I)
FOR i = 1 TO 50 APPEND BLANK
ENDFOR
INDEX ON iData TAG iData CLOSE ALL
USE randData SET ORDER TO iData GO TOP LIST NEXT 10 && First 10 (end-of-line comment) SKIP 81 LIST NEXT 10 && Last 10 CLOSE ALL
FROM randData ; ORDER BY iData DESCENDING ODBC Access using SQL Passthrough
LOCAL nHnd nHnd = SQLCONNECT ("ODBCDSN", "user", "pwd")
LOCAL nResult nResult = SQLEXEC (nHnd, "USE master") IF nResult < 0 MESSAGEBOX ("MASTER database does not exist!") RETURN ENDIF
LOCAL cAuthorID, cAuthorName cAuthorID = "1001" cAuthorName = "New name" nResult = SQLEXEC (nHnd,"UPDATE authors SET auth_name = ?cAuthorName WHERE auth_id = ?cAuthorID")
SQLDISCONNECT(nHnd) BETA CODE NAMES
EXTERNAL LINKS Microsoft pages
Other pages
REFERENCES |
|
|