We have solved the problem: the most difficult part was getting to view the log file Excel had created!!
I'm not a total newbie, but I could not believe that when you view a folder you can access a subfolder just typing its name in the address bar, even if the same subfolder is not shown in the list (note: I had checked "View hidden files" and even "View system files"!!).
With the help of the log file, we found the error and fixed it opening the file in text mode and correcting the Autofilter section of the xml code:
<AutoFilterColumn x:Index="2" x:Type="Custom">
<AutoFilterCondition x:Operator="Equals" x:Value="8436"/>
</AutoFilterColumn>
<AutoFilterColumn x:Index="8" x:Type="Custom">
<AutoFilterCondition x:Operator="DoesNotEqual" x:Value="SI'"/>
</AutoFilterColumn>
<AutoFilterColumn x:Type="Custom">
<AutoFilterCondition x:Operator="DoesNotEqual"#REF! x:Value=""/>
</AutoFilterColumn>
</AutoFilter>
I just had to remove that "#REF!" string that had corrupted the code.
I still can't believe I fixed an XML error being only a Cobol programmer and VB newbie, now I have to think what my colleague will have to treat me to, being she the actual owner of the file and the one who was about to go crazy for losing two days' work!!
I hope this case will help someone in this wonderful community.