Yes I did. In fact, I caught your thread while searching for the original thread where I posted the issues. I heard back from them today and received some resolutions to my problems with version 5.1. Actually, they turned out not to be problems, but a difference in the way 5.1 handles errors from version 3.5. I had some problems where the dll was detecting errors but not fixing them. I had to open them up in the gui in order to do a full repair. Of course, that means that any customers out there using my app will have to send the tables to me for a complete repair if the dll cannot repair it in either stealth mode or manually. Here is a portion of their reply to me:

---------------

The FoxFix DLL is designed to be included in applications thus will
only repair items that are deemed 100% *safe* to update. Therefore some
errors will not be fixed in the header unless there is a reference
header in the 'Header Archive' for that particular file. This is why
the DLL was telling you something was wrong but would not fix your
files.

FoxFix 5.0 detects many errors that Visual FoxPro will just live with
and that FoxFix 3.5 will not detect. FoxFix 5.0 is designed to be
strict to stop errors propagating into far more severe errors.

The underlying idea is that files are checked and any errors fixed in the GUI
first. This gives you 100% error free files at the start and
generates the 'Header Archives' for use with the DLL when you come to
deploy your application.