Antiquated Software

[Stanley Barnett]

About the life cycle, that was a question 2 years ago, but the answer is NO,
as Microsoft has officially committed resources well into the next decade.
Just check out the new stuff that came in VFP 9.  VFP can natively talk true
SQL, do full API stuff, integrate seamlessly into Office applications and
etc.  Versions prior to 9(current) used a subset of SQL, but now its true,
with commands that can utilize older versions of SQL.

The 2gb limit is still there on native tables, but when designing a new app
all you need to do is separate your data, then you are not tied to it,
instead when the time comes, just move the data tier to SQL, or whatever via
a data connector.  No matter what data backend you use, you have at your
fingertips VFP's awesome power of its data manulapation engine creating
local cursors and etc, which all the languages lack. 

VFP is also .Net compliant...  and we all know that .Net is currently
defined as the future.

Stanley


 

-----Original Message-----
From: Scott Walker [mailto:scottw1 at alltel.net] 
Sent: Thursday, January 19, 2006 1:25 PM
To: 'Stanley Barnett'
Cc: Filepro_List
Subject: RE: Antiquated Software

Stanley Barnett wrote:

I really did not start this to be starting something, as you will see
very
little posts from me over the years.  But when people start telling
others
things that I know is Not True, then the audience needs informed.  I
even
went on to say that I would help anyone with the knowledge and
experience
that I have acquired transitioning from filepro to VFP.



Stanley,

Isn't VFP at the end of it's life cycle too.  At least it seems like a
product that's not going to be fully carried into the future with things
like handling over 2gb file sizes,etc?  

Regards,

Scott

Scott Walker
RAM Systems Corp.
Scottw1 at alltel.net