>>And SQL Express ( or for that matter MSDE ) means a lot of us haven't used DBFs for our VFP apps for years. One code base scales from mom and pop to enterprise.
>
>Absolutely.
>
>MSDE/SQL Express can handle the database needs for an awful lot of small/medium business needs with reliability and security that VFP tables can not match. Free.

When properly 'powered by VFP' then yes :).
However, next to licence itself there are also administration/maintenance costs I wld say, while 2gb overall size limit makes it really mom/pop only.
[and they better hv son as SQL admin :)) ]

On the other side I disagree about DBC/DBF weakness theory. When properly set/programmed you will not hv ANY problems. Fact that meny people did not bother to take advantage of buffering/transactios and this way increased data reliability is another story.

I think that initial complexity of fully adopting OOP and new database possibilites as far as back in VFP5, kind of did it's part in fact that
meny ordinary inhouse developers (and some shops to) in fact never harnessed full VFP power (meny people compiled FPD apps/data directly to VFP remember).
Imho, that is one of main reasons why corruption become bad buzzword associated with VFP.
Imho buffering / transaction tracking should hv been natively embeded within VFP dataengine as far as back with VFP6 and then I wld like to hear what are real percentages of corrupted dbcs/dbfs data losses etc.

Whatever... I am gonna turn this into another VFP demise rant so I better stop :)