>>We have an application used by people on their home computers and we are having lots of problems with corrupt DBFs, because they constantly turn off their computers, have power outages, kids turn off the machine, etc. No amount of "training" has helped. So, we're wondering does MSDE have corruption problems like DBFs? Would MSDE be more stable in such an environment?
>
>The problem is not in coruption of the database - they will have the same problems with MSDE.
>The problem is in wrong done VFP application.
>You work directly with open tables and when your customers turn off the PC this crash the databases. Solution is to use cursors.
>HTH

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.