Tracy,

Unfortunately, I haven't done any more work on it, nor resolved anything, since I posted this message. Frankly, I was quite disturbed because I did not get a return call, nor a return email from xitech.

After I got the dscan50x.app to work I let it go at that. At some point, however, I do need to revisit this. I will let you know if I make any progress, and I would greatly appreciate if you let me know of your progress as well.


Thanks.

Sorry I couldn't help.


>David,
>Did you ever resolve this issue? I have FoxFix 5.1 and am running into the same problems and some additional ones. As far as the additional problems go: I have 4 tables that ff_scan() returns errors on (but does not appear to be valid errors and it does NOT fix them), however I can open the tables fine in VFP. If I scan them with FoxFix 3.5, they return 0 (no errors). Strange... Trying to figure it out. The tables are type fox2x for compatibility issues. I want to implement the distributable dll with an app so I need to get the ff_scan working right.
>
>Also, if I try to open the tables after running ff_scan on them, I get the 1705 error (file access denied). I have to close the app that runs foxfix completely before I can attempt to recreate or rebuild the files that foxfix has scanned (either returning errors or no errors -doesn't matter). Any ideas on how to get the tables all closed? I've tried flush and fflush() after running ff_scan() on them with no success.
>
>
>Tracy
>
>
>
>>Since I posted this, I have some additional information:
>>
>>For some reason, I am not able to get foxfixes ff_scan function to work right. it returns an error code of zero on a table that I know is corrupt.
>>
>>But I implemented a function call to 'dscan50x.app', and this is working like a charm. It finds and/or fixes the problems that I can't find with ff_scan() and fixes the problems I can only find, but not fix.
>>
>>But I still can't get Foxfix5.exe, via the gui interface, to write the changes to my tables.
>>
>>Any ideas?
>>
>>TIA
>>
>>>I have an email in to Xitech - but since it is late at night there now.. thought I'd try here first..
>>>
>>>I just got a new version of Foxfix - 5.1. I ran the standalone version to check the integrity of my dbf. Fox fix found errors in the fpt. (However the 'Memo Tab' itself has a green checkmark next to it) But the scan summary tab shows that there were 23 memo pointer errors. The 'messages' tab shows a final status code of '0000..' (Doesn't that indicate that there is no problem?
>>>
>>>However, the 'error log' tab shows 23 messages indicating memo pointer problems. Clicking the update button at the bottom right takes me straight back to the 'Filename to scan ' dialog box. When i click to scan the file again, it shows the same errors. The dbf and fpt never get updated.
>>>
>>>What am I doing wrong? Why does the memo tab itself have a green checkmark?
>>>
>>>
>>>I found an 'old version' of foxfix from around 1997. It had a separate memoscan utility. I ran that against my table(s). It found and corrected the memo errors. I'm sure they have improved the product since 1997! not made it worse - so - I must be doing something wrong - need a new build -.
>>>
>>>Env: win98, don't think there are any file or folder permission issues, etc.
>>>
>>>Finally, I used the ff_scan function of the foxfix5.dll - it is NOT finding any errors with the file. Again, I am guessing that I am doing something wrong.
>>>
>>>Any ideas?
>>>
>>>TIA