Epipgx
asked on
Excel 2013 custom toolbar loading
I have a custom toolbar that is created via an addin. The addin is stored in the Roaming addins folder under my use profile and should load whenever Excel opens.
Since switching to 2013 (64 bit) I have noticed that the addin performs fine unless I use right click from the taskbar to open a recent file. If another version of Excel was open with the addin loaded the addin is there but if the right click was the first instance of excel opened the addin fails to load.
Does anyone know why this might be and how I can prevent it?
Since switching to 2013 (64 bit) I have noticed that the addin performs fine unless I use right click from the taskbar to open a recent file. If another version of Excel was open with the addin loaded the addin is there but if the right click was the first instance of excel opened the addin fails to load.
Does anyone know why this might be and how I can prevent it?
ASKER
I was on 2007 32-bit. It is an addin I have written to create a toolbar to allow quick access to lots of macros called ExcelMacroBar.xlam.
did you use the VBA7 declation in your addin?
#if Vba7 then
' Code is running in the new VBA7 editor
#if Win64 then
' Code is running in 64-bit version of Microsoft Office
#else
' Code is running in 32-bit version of Microsoft Office
#end if
#else
' Code is running in VBA version 6 or earlier
#end if
#If Vba7 Then
Declare PtrSafe Sub...
#Else
Declare Sub...
#EndIf
#if Vba7 then
' Code is running in the new VBA7 editor
#if Win64 then
' Code is running in 64-bit version of Microsoft Office
#else
' Code is running in 32-bit version of Microsoft Office
#end if
#else
' Code is running in VBA version 6 or earlier
#end if
#If Vba7 Then
Declare PtrSafe Sub...
#Else
Declare Sub...
#EndIf
ASKER
No and the addin loads and works perfectly except in that one very specific instance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
To be clear, you don't need to use conditional compilation unless you want different code bits to be compiled for different constants/architectures (whatever the constants refer to). So long as you don't have anything that won't run in 32-bit and 64-bit there's no need for it at all. If you're using API's that won't compile the same in 64-bit as they do in 32-bit then you're fine. You can even use the PtrSafe in 32-bit so long as it's VBA7 (2010 or later).
Zack
Zack
ASKER
the original question was a setup error not something an expert could have offered advice on.
most of the add-ins support 32bit version? is it a commerial add-in? it has a name?