|
Why are you still developing applications in FoxPro?",
I get this question a lot. There is a misconception that FoxPro is old
technology, is going to be phased out, or has been replaced by Access. The
question of FoxPro versus Access has been around since Microsoft purchased
FoxPro from Fox Software.
It is difficult to compare these two programs. The simple answer is FoxPro and
Access is two distinct products designed for two distinct markets. Access is an
end-user product designed to be easy for the end-user to capture, process and
report on small amounts of data (under 100,000 records). FoxPro is a development
tool, fully object oriented, designed to process millions of records and
functions very well either as the back-end of a moderately complex solution or
as the middle tier of a very complex one. Each has it's own place in the
software world, but there really is no direct comparison. It's like saying
"Which is better, Notepad or Word"? The answer is of course "It depends on the
job you are trying to do!"
As a software developer I would never consider using Access it just does not
have the flexibility and power need to develop robust multi-user applications.
If you are working on a short-term in-house project that is going away in 6
months use Access. But if you are building something that is going to be around
for the next 5 years use FoxPro.
Ask an Access developer for customer references from customers who have had
their applications running for 5 or more years, you will not find many. Do the
same for FoxPro developers I personally have 5 applications running 5 or more
years and 3 of those are mission critical.
More about developing application in foxpro:
Advantages
Why Not Access
What other have to say:
Will your
software project succeed
Visual
FoxPro General Q & A
http://www.foxite.com/archives/0000013007.htm
http://www.pafox.org/vfps_role.htm
Download the Microsoft
Whitepaper: Choosing the Appropriate Database Development Tool
|