Hi Robin !
A) VFP is as realible as underlaying hardware/OS.
First check things on hardware/OS layer
1. Turn off disk caching !
2. Check NICs, cables and switches/hubs
3. Assure that server machine and workstations use UPS boxes
and server is not switched off when workstations are working with data.

B) Bad news - there is no tool that can recover corupted data in 100% in all cases of table coruption - goto point (A) rather.
Good news - on W2000 with good hardware VFP should work stable.

C) From my experience it seems that VFP7 is a little bit more stable then VFP6 - but it is only my impression. VFP7 has great features like much better help, intellisense, task list, XML and web services support so work with VFP7 if it is possible.

D) If data integrity is very important VFP with MSDE (or with SQL Server) would be much better choice than VFP alone.

Hope this help.


>Please help,
>
>FoxPro 6 - Servicepack 5 - Windows 2000 Pro
>
>We are getting problems with error 41 (Memo file "name" is missing or is invalid (Error 41)). We are looking for a way to manage the problem. Can anyone help us with ANY of the following questions :-
>
>1. What causes this problem. What steps can we take to avoid situations where we are vunerable.
>
>2. If we get Header Corruption i.e. 'Not a table', can we fix it without FoxFix ?.
>
>3. How good are are the Fox Fix distribution components. Do they work and are they reliable ?.
>
>4. What problems have you had with error 41 and how do you manage the problem ?.
>
>5. We are planning to write a product in FoxPro that needs to be as data corruption free as possible. Will FoxFix help here or do you find that all of your apps have data corruption problems regardless ?.
>
>6. Does FoxPro 7 have any improvments in data robustness and data management.
>
>7. What are the alternatives to FoxFix if any ?.
>
>I know there are a lot of questions but your help will be very much appreciated and will help us in making some important decisions.
>
>Thankyou very much.
>
>Robin Das