OpenFileName = Application.GetOpenFilename Crashing Excel 2016 (64bit)

Hi,

We have a customer that is running Excel 2016 64bit (yeah, I know, 64bit is not recommended but they have to have it for a specific system they are running so I can't just uninstall and install 32bit).

They have a spreadsheet with macros that has been running perfectly for months and now is suddenly crashing Excel on execution. I presume this is due to an update to Office or possibly VB.

At this point I should point out that I did not program this, it was written by a third party that the customer used direct and is no longer available... sigh.

By debugging the code I can see that is this section that crashes excel. The red line being the exact line that knocks it over.

Function OpenWorkbook() As Workbook
OpenFileName = Application.GetOpenFilename("Commission Spreadsheet,.xls; .csv; xlsm")
If OpenFileName = "False" Then Exit Function
Set OpenWorkbook = Workbooks.Open(OpenFileName) 'Get data
End Function

The crash details are the usual help.

Problem signature:
Problem Event Name: APPCRASH
Application Name: EXCEL.EXE
Application Version: 16.0.8326.2096
Application Timestamp: 59a4b539
Fault Module Name: EXCEL.EXE
Fault Module Version: 16.0.8326.2096
Fault Module Timestamp: 59a4b539
Exception Code: c0000005
Exception Offset: 000000000000f4c1
OS Version: 6.3.9600.2.0.0.16.7
Locale ID: 2057
Additional Information 1: 6a67
Additional Information 2: 6a674c7f3fabe4c0e6f373aa32e1c003
Additional Information 3: f11d
Additional Information 4: f11da28a6897dbe58e97a75b0c4e7512

Any suggestions would be very much appreciated.

Without the ("Commission Spreadsheet,.xls; .csv; xlsm") bit amended on the end it starts up the browse for file window and all works fine.

As it happens, the customer is now happy that its all working now that I have removed that bit and its doing what it should so I'm not really sure what that bit was used for?!

With that in, it crashes before the browse for file window ever appears.

Oh well, they are happy its working as they need it without that bit so not to worry!

Thanks for your help Bram

Hi,

Seems like recent Windows patch update causes excel to crash while executing the application.getopenfilename method. Using Application.FileDialog property instead of Application.GetOpenFileName worked for me.