(While some 'solutions' are shady on, it's a good place to look initially).Īs far as any 'new syntax', I have no idea.For Administrator of Enterprise: To deploy this software in your organization or enterprise and change the default settings for all users (for example: more than 50 users), the MSI file (Microsoft Installer file) is recommended. In this case, it is important HWND is IntPtr (this is because a HWND is a 'HANDLE' which is void*/'void pointer') and not long. The ShellExecute function has a signature of: HINSTANCE ShellExecute( It's the bitness of the execution context (VBA/CLR) which is important here and the bitness of the loaded VBA/CLR depends upon the bitness of the host process.īetween 32/64-bit calls, most notable things that go wrong are using long or int (constant-sized in CLR) instead of IntPtr (dynamic sized based on bitness) for 'pointer types'. (The 'issue' is Office running in 64-bit mode). If you run Office 2010 32-bit mode then it's the same as Office 2007. In any case, this reply may be useful to someone. 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 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

Update office 365 64 bit