Excel files crashing when upgrading to 64bit Excel

I have a bunch of Excel files heavy with VBA code. This Excel were created by a programmer in Excel 2010 32bit. When we upgraded to Excel 2013 64 bit in our company, these Excel files began to generate problems: we were able to fix declarations and use those files, however in repeated instances these file began to crash when enabling the macro content. Files without VBA content never crash.

I have found a workaround:

1. Open the workbook in Excel. Normally Excel will disable macros in a worksheet until you click a button to enable the macros. Do not enable the macros just yet.
2. Open the VBA editor. You can hit ALT+F11 or on the ribbon click Developer > Visual Basic
3. In the VBA editor double click your module or first module that contains your project. Add a commented line of code such as:

‘ This is a comment

Then click on the Debug menu at the top and click Compile VBA Project.

Repeat this step for each module in your workbook and then save the workbook.

4. Close the workbook and re-open it and enable the macros and test it.

However, some of the files that were recompiled keep crashing.

My question is:
-is there a viable and stable solution?
-what is in fact the source of the problem?

Excel 64 bit, will crash frequently on PCs with 32bit OS.
Excel 32 bit, will crash frequently on PCs with 64bit OS.

Hi !

I agree with romperstomper, I use different Excel 32 bits version on 64 bits OS (Seven or Windows 8) and no crash issue …

And since 2010 version, Microsoft itself advises to install in 32bits !

In 64 bits, many codes are to be modified if they use Declare statement for API (search for PtrSafe mod).
But some APIs do not exist in 64 bits versions or give issues …

Just to clarify, OS is 64bit. Files were originally generated in OS 32bit / Excel 2010 32bit enviromnment, they crash now that we are in OS 64bit/Excel 2013 Environment.

Also, all declare statements have been modified (Ptr to PtrSafe).

Originally Posted by romperstomper

Was that all you changed in the Declares? You usually need to do more - some Longs need to be LongPtr or even LongLong.

i will verify that. Ptr to PtrSafe for sure. However, would that cause the excel file to crash or rather would it just be that the Excel cant be used (as it was before I changed the declarations Ptr to PtrSafe)?

These are the declarations:

Private Declare PtrSafe Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As Long)

Private Declare PtrSafe Function OpenClipboard Lib "user32" (ByVal hwnd As Long) As Long
Private Declare PtrSafe Function CloseClipboard Lib "user32" () As Long
Private Declare PtrSafe Function GetClipboardData Lib "user32" (ByVal wFormat As Long) As Long
Private Declare PtrSafe Function EmptyClipboard Lib "user32" () As Long

'CreateMetaFileA DeleteEnhMetaFile
Private Declare PtrSafe Function CopyEnhMetaFileA Lib "gdi32" (ByVal hENHSrc As Long, ByVal lpszFile As String) As Long
Private Declare PtrSafe Function DeleteEnhMetaFile Lib "gdi32" (ByVal hemf As Long) As Long

Right, there is not only PtrSafe but also Long. That said, again, would that be an issue that results in a crash of the Excel file or rather something that simply will not allow me to open this Excel file?

Miraun,

thank you for very much for your reply. I am also quite convinced that it is not the code.

Having said that, if I enable VBA support, that would mean that I receive automatic updates to fix compatibility (or does it simply mean that I can escalate this to MS and they can provide me an answer)? Sorry the stupid question, but I am total noob

Hi accicarelli,

I agree with what the previous posters have to say. Upgrading from 32 bit Excel to 64 bit Excel is not trivial, especially if VBA is involved. Issues you have to be concerned with include:

a. API function declarations and usage. For example your OpenClipboard declaration in post #8 is probably incorrect. You have:

Please Login or Register  to view this content.

The Microsoft master file contains:

Please Login or Register  to view this content.

b. Some items that were provided in previous versions of Excel are no longer available in 64 bit Excel such as the DatePicker that was previously available in file mscomct2.ocx.

c. You may have problems with 'Active X' controls created in 32 bit Excel.

d. ...and there is more that nobody knows about yet.

Lewis

I have tried the solution described here:

http://blogs.technet.com/b/the_micro...ing-macro.aspx

and it seems to work for a while, but then the same file--which had worked for a while--go back to crashing.

Could you please provide link where I can find correct declarations? Thank you for pointing out the mistake in the code I provided

Also, if I were to provide a code to a "VBA wizard" would that person be able to fix the issue looking at the code (and the file), or is this something that has been difficult to grasp also for VBA Excel experts? Seems to me, having searched online for almost a year, that this issue is creating difficulties to a lot of persons.

Thanks for help