Corrupted Excel xlsb (binary) file

[DEksel]

Actually, subject. Any medicine for this? Need only VBA of course...

Blocking excel with tough resource eating... can't open and can't see anything... Office 2016, Windows 10.

Thanks in advance.

 

[Dan_W]

Strange. So it doesn't present any kind of error message or any message at all?
Is it an XLSB file that was generated by Excel following the crash of Excel and is a recovered file? If so, what kind of file was it originally (XLSX? XLSM? etc?)
This is a ssomewhat random question, I know, but what is its file size? I ask because when my Excel generates XLSB files following a crash, a dead giveaway that the recovery process failed is that the XLSB file size is 2kb.

 

[DEksel]

Strange. So it doesn't present any kind of error message or any message at all?
Is it an XLSB file that was generated by Excel following the crash of Excel and is a recovered file? If so, what kind of file was it originally (XLSX? XLSM? etc?)
This is a ssomewhat random question, I know, but what is its file size? I ask because when my Excel generates XLSB files following a crash, a dead giveaway that the recovery process failed is that the XLSB file size is 2kb.

Here is about fileformat XLSB

What is an XLSB file?

Your file format guide to know what is an XLSB file and APIs that can create and open them.

docs.fileformat.com

Excel didn't generate anything. XLSB format is binary excel file that I've created by myself. Much faster than XLSM. These guys
Online XLSB to CSV Converter | Free GroupDocs Apps (xlsb-to-many various file-types)
can extract your worksheets from corrupted XLSB file but can't do anything with VBA codes (modules).

I've deleted that file already. Let's say, problem solved.

 

[Dan_W]

I'm very familiar with the XLSB file format, and it's speed benefits. Of course, this also works against it - because if it were an XLSM file, you might have been able to extract the VBAProject.bin file (which houses the VBA code).

XLSB files are (sometimes) generated by Excel for documents that are open when it crashes - which is why asked, and why I also asked that - if that were the case - what was the original file type... Because when you load a workbook that you then "can't see" (as you described), my immediate thought is that it is an XLAM file for example. That obviously is not the case here though.

Sorry that you weren't able to resolve it, though. I hope that you didn't lose any important code.

 

[Marc L]

I met less issues with .xlsb than with .xlsm workbooks.​

​

A common issue is using some ActiveX instead of Form controls whatever in worksheets or userforms and​

sometimes working with 64 bits Excel versions …​

​

Another one is using a huge number of cells with some conditional formatting.​

​

As any VBA module can be exported as a backup …​

 

[Dan_W]

Another one is using a huge number of cells with some conditional formatting.

Really? I had no idea that this can lead to corrupted files - I tend not to use much conditional formatting, but it's helpful to keep this in mind. Thank you.

 

[Marc L]

I met this case a few times and I did not seen anything else in the users habits.​

But as it may also lead from the computer OS environment …​

 

[Dan_W]

Any thoughts about Out of Memory issues? I've been working on a coding project that converts VB6 code to be VBA compatible, and builds VB6 Foms as VBA Userforms, and all is good until such time as you try and close one of the newly created workbooks. At which point, there is cascading failure and the entire Excel instance just disappears (after advising me about how it is out of memory).

 

[Marc L]

​

Excel is the worst pro application in term of memory management I have ever seen …​

Using UserForms can be a mess : the more objects, the more chances to have some issue.​

Do you use ActiveX or multipage elements ?​

​

If you are under a 64 bits Excel version try to build the same on a 32 bits version …​

 

[DEksel]

A common issue is using some ActiveX instead of Form controls whatever in worksheets or userforms and​

sometimes working with 64 bits Excel versions …​

​

Another one is using a huge number of cells with some conditional formatting.​

​

As any VBA module can be exported as a backup …​

Nothing simillar in those WB. Simple, MS Files are sometimes corrupted. I have so many procedures and modules. Most of them are saved as BAS. This was the case when I wrote something new and lost about 2 hours of work... nothing terrible... I wrote all of that again in 40-50 minutes.