Re: Preparing VFP programs for SQL Server
- From: tim_witort@xxxxxxxxxxx (Tim Witort)
- Date: Tue, 27 May 2008 13:46:22 -0500
Zootal seemed to utter in news:O8JVwW5vIHA.420@xxxxxxxxxxxxxxxxxxxx:
The architecture of the VFP database is such that it's not a server
database, and very susceptible to corruption. I wouldn't even call it a
DBMS as it lacks security and fault tolerance, and does little to
enforce data integrity. All you have to do is fart on it and your data
becomes corrupted. This you are already painfully aware of :-).
Oh, come on. VFP databases certainly lack a lot of the benefits
of an Oracle or SQL Server DB, but they aren't *that* fragile.
I've been running VFP apps for the past 15+ years with
thousands of databases (yes, thousands) and I can count on
one hand the number of times I've had corruption problems.
And none of them resulted in lost data - only index rebuilds.
VFP isn't the right DB for every situation, but neither is
Oracle. And VFP can stand up to a fart as well as the
next RDBMS. :^)
-- TRW
_______________________________________
t i m . w i t o r t
_______________________________________
.
- Follow-Ups:
- Re: Preparing VFP programs for SQL Server
- From: Villi Bernaroli
- Re: Preparing VFP programs for SQL Server
- From: Zootal
- Re: Preparing VFP programs for SQL Server
- References:
- Preparing VFP programs for SQL Server
- From: WP
- Re: Preparing VFP programs for SQL Server
- From: Gene Wirchenko
- Re: Preparing VFP programs for SQL Server
- From: WP
- Re: Preparing VFP programs for SQL Server
- From: Zootal
- Preparing VFP programs for SQL Server
- Prev by Date: Re: Interesting Programming Problem
- Next by Date: Re: a locked table
- Previous by thread: Re: Preparing VFP programs for SQL Server
- Next by thread: Re: Preparing VFP programs for SQL Server
- Index(es):
Relevant Pages
|
