excel ExportAsFixedFormat does not work in .xls when updated to windows 11

[Yveske]

Hi,

I had some VBA code which creates a pdf from an excel file (.xls).
This worked without a problem.
Since yesterday my computer is updated to windows 11 and now this code does not work anymore.
When I open the .xls file, it gives an error on the line with 'ExportAsFixedFormat'.
When I save my file as .xlsx and then run the code, then there is no error?
Does anyone have an idea why this doens't work in my .xls file?
Maybe a setting in windows ?

Thanks

 

[Joe4]

I am using Windows 11, and that block of code appears to be working fine for me.
You don't have any hidden sheets, do you? That could cause issues.

Note that you may want to verify that you are create a valid file path and name. You can do that by adding this line of code just before that "ws.ExportAsFixedFormat..." line:

MsgBox "Filename is: " & spath & sBestand & ".pdf"

This will return to the screen the full file path and name of the PDF file you are trying to create.
Make sure that the path and file names are valid, and that you have rights to create files in that folder.

 

[Yveske]

Hi,

when running the code in an excel file with extension '.xls', the result is:

When running the code in an excel file with extension '.xlsx', the result is the same:

The folder 'Data' exists as you can see below.

So 2 times the same file name and location, but the difference is that the file is saved when the code is running from an excel file with extension '.xlsx', but not saved from an excel file with extension '.xls'.

 

[Joe4]

Where is the VBA code stored?
Is it stored in the same workbook as where the data resides?
If so, it should have a "xlsm" or "xlsb" extension, as "xlsx" extensions cannot contain any VBA code.

If it is stored in a separate file, where in your code are you opening this data file?

 

[Yveske]

The VBA code is stored in an add-in, which is loaded into excel.

 

[Joe4]

I don't know. I ran some test of that section of code on both "xls" and "xlsx" files, and both seemed to work just fine for me.
So I cannot recreate your problem.

Are you sure that there isn't any issue with that one file?
It isn't protected, locked, or stored in a location you cannot write to, is it?

Not really sure what else I can do since I cannot recreate the scenario you are describing.

 

[Yveske]

No there is no problem with the file.
I tested even with a new file saved as '.xls' and saved as '.xlsx'.
In the first case, 'xls' file, I receive the error.
In the second case, 'xlsx' file, the pdf is generated.
Strange issue.
Anyway thanks for looking into it.

 

[Joe4]

You are welcome.

Sorry I could not help more, but I cannot see any issue. It could be an environmental or network issue. Not really sure.