I thought VBA now run on the CLR these days, but it does not. This answer is likely wrong wrong the context. Note that in the old VB6, PtrSafe isn't even a valid command, so it'll appear in red as though you have a compile error, but it won't actually ever give an error because the compiler will skip the first part of the if block.Īpplications using the above code compile and run perfectly on Office 2003, 2007, and 2010 32 and 64 bit. You will, of course want to make sure that the library you're using is available on both machines, but so far nothing I've used has been a problem. Private Declare Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" _ Private Declare PtrSafe Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" _ (ByVal hwnd As Long, ByVal lpOperation As String, ByVal lpFile As String, ByVal lpParameters As String, ByVal lpDirectory As String, ByVal nShowCmd As Long) As Long
#Office 2010 64 bit incompatible with office 365 64 Bit
I've already encountered this problem on people using my in-house tools on new 64 bit machines with Office 2010.Īll I had to do was change lines of code like this: Private Declare Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" _
The only circumstances under which it won't work is Office 2010 64-bit on Windows 64-bit. However, per David's answer below, I was mistaken about the circumstances in which my Declare statement won't work. I have a VBA application developed in Excel 2007, and it contains the following code to allow access to the ShellExecute function from Shell32.dll: Private Declare Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" (ByVal hwnd As Long, ByVal lpOperation As String, ByVal lpFile As String, ByVal lpParameters As String, ByVal lpDirectory As String, ByVal nShowCmd As Long) As Long
0 kommentar(er)
