Has anyone had any luck fixing corrupted h2k files?  I ran the xml through a syntax checker and it says everything is ok.  looking through the file it appears fine as well.

FTR:  I used the file to infer a xml schema in Excel.  After that it was no longer accessible in h2k.  This seems odd as I believe Excel just reads it, it doesn't modify it.

Jeffrey, I assume that you can't get a backup of the h2k file that was before running it through Excel? If you can, you should run a file compare on the two files.

If not, get a working h2k file, save a copy, and run it through the same process with Excel that broke your original file. Then do a file compare to see what's different. Its probably not XML syntax that's broken, but modified data that Hot2000 isn't happy with.

Stan

Jeffrey St-Pierre wrote:

Thanks for the advice.  These are dummy files that I was using to create extraction schemas, so nothing important.  Therefore I didn't back it up.  i.e. I am unable to do a "diff" on it.  I'll see if I can reproduce the error.

Excel frequently will save and over write data.   Also it will lock the file while it is open and for up to a minute after closing the file.  Suggestion:  always use a backup file to do experiments (especially with excel).

Jeffrey St-Pierre wrote:

Has anyone had any luck fixing corrupted h2k files?  I ran the xml through a syntax checker and it says everything is ok.  looking through the file it appears fine as well.

FTR:  I used the file to infer a xml schema in Excel.  After that it was no longer accessible in h2k.  This seems odd as I believe Excel just reads it, it doesn't modify it.

One thing I've ran into - may be unique to my process but it might be the same error. Try to open the file in a basic notepad and Ctrl+F to find "housefile". A common corruption in my files has been it duplicates the end portion (often 8-10 lines, sometimes more) so it has extra data after the end housefile code.

Usually in this case it can still run HOT2000, but won't work in the report generator.

I've had other corrupted files that were just a write off - not worth trying to find the code break.

The fix - you have to save a new copy - sometimes using notepad to delete the duplicated code won't be updated in the .h2k file - but saving it as a new file will - then just rename (remember the .h2k at the end of the file name).