Brenda:
Right now we distribute a seperate exe which is run like a fixit program when necessary. It's a very brute method with very little feedback as to success or not (though it hasn't failed yet). The program is based on the fixall.prg that should have been unzipped into your root foxfix directory. Looking at the code now I can see that we had to modifiy the loadfix.prg like so:

DO CASE
CASE '2.0'$VERS(1) and Substr(Vers(1),1,6) == "Foxpro"
cFixVer = "FFIX3_20.PLB"
CASE '2.5'$VERS(1) .OR. '2.6'$VERS(1) And Substr(Vers(1),1,6) == "Foxpro"
IF 'WIN'$UPPER(VERS(1))
cFixVer = "FFIX4_25.FLL"
ELSE
cFixVer = "FFIX4_25.PLB"
ENDIF
CASE '3.0'$VERS(1) And Substr(Vers(1),1,6) == "Visual"
cFixVer = "FFIX4_30.FLL"
CASE '5.0'$VERS(1) .OR. '6.0'$VERS(1) And Substr(Vers(1),1,6) == "Visual"
cFixVer = "FFIX4_50.FLL"
OTHERWISE
WAIT "Version Not supported" WINDOW
CANCEL
ENDCASE

This was necessary because our VFP serial number had a 2.0 in it!

>How do you send it as a seperate app, like a fixit program that you have the client run? Do you use the foxfix5.dll? If you do not mind, i would like to see your code. Still trying to get the hang of it although I have talked with the xitech europe tech support and they have been very helpful.
>
>Brenda
>
>
>>Brenda:
>>I haven't used it from within an application. I have used it as a seperate >application that I send with our distributed app. We only run it when we get >an obvious table corruption, and it has worked every time.
>>
>>Mike
>
>>>Finally convinced my boss to buy FoxFix. Well I have spent several hours reading and playing and it is not very intuitive. At least not for someone who does not have a good understanding of the file structures.
>>>
>>>Has anyone used the DLL in your application and how did you use it. Wondering if I should check my tables at the beginning everytime my app is run, should I let it correct the errors or just report them, etc. Some guidance would be appreciated.
>>>
>>>Brenda