>From my experiences I found the urban legend of VFP and corrupted files not to be true. Maybe in the Foxbase year but not VFP.
>
>File corruption has not been a problem for me so I would advise you to make your decision on some other basis other than file corruption.

I remember several possible causes for table corruption:

DOS 5.00
Bad network cables
Bugs in file server OS (fixed by upgrading then Novell 4.0x to 4.0x+3)
User turning the machine off (but that was fixed by someone else opening, editing and then closing the tables on server)
Someone unplugging the network cable (still fixable in the next minute or so before the server flushes the buffers)
Power blackouts

Hadn't seen any of these for quite a while. And with buffering, it actually takes a powerout at some special moment to screw the tables.

I do have one user who regularly manages to have a corrupt memo file, on tables he creates for himself. Don't know what he's doing, that's nobody's app, just a simple form he builds for himself. The funny thing is that he always manages to keep working with such a table without noticing anything funny.