>>In my application a table is opened for a very short moment only at the start and the quit of the application. In the table is entered simple information who and when enter or exit the program and the table sometimes(very rarly) got coruption. Unfortunatly it is not enough to close a table to avoid coruption. Data can be still in disk cache. Simple coruption can be repaired using tools as SDT. So I think that in case of simple one user application we can achieve acceptable level or realibility. But in case of complex multiuser application is very probable that in a corruption will participate several tables and automatic repair fails.
>
>We create our own data access classes, which open data, read data and close tables. All data which apps use we keep in the memory, as cursors. Classes make updates of the tables when we save data. Example of them you can find at our desktop VFP2002 Tournament code download #14280
>If appears probles with tables in our admin part is implemented DataTool1.0 download#12963.
>If some thing happens with EXE user can easily to reinstall from setup.
>With this technologies we reduce our client support

I agree that such technology can reduce clients calls. But does it mean that you completly eliminated VFP table coruption ?