converting access 32 bit code to 64 bit

[markjkubicki]

Our office has an unfortunate mix of Access 32bit and 64 bit; unfortunate because the code had been written in 32.


Till now, I've simply had everyone uninstall their 64bit Access from office, and download the 32bit runtime version... (admittedly, a patch, but effective)

It's come time to bite the bullet and add the "what version are you using" code and all the related caveats (for another year or so, BOTH versions will exist within the user group)"; A while ago, when this problem first showed up, I was able to find several articles and forums on declarations, long vs. short, and all those necessary things to know / do... This morning, I'm finding stupid.

Would someone direct me to the correct aisle in the library stacks?

big thanks in advance,
mark

[markjkubicki]

OK... so I found some stuff about Declare PtrSafe Function and LongLong
but, I'm not sure how to use it...

I'm working in WIN32 and NOT VBA7
The code will need to run in both 32Bit and 64Bit versions of ACCESS

I've revise a line of code to handle both:

_____________
If VBA7 Then
Private Declare PtrSafe Function apiGetUserName Lib "advapi32.dll" Alias _
"GetUserNameA" (ByVal lpBuffer As String, nSize As Long) As Long '? change to be LongLong ?
Else
Private Declare Function apiGetUserName Lib "advapi32.dll" Alias _
"GetUserNameA" (ByVal lpBuffer As String, nSize As Long) As Long
End If
_____________

and before I can even get to the LongLong stuff, I get this error:
"Compile error: Expected: Sub or Function" on PtrSafe"

maybe I need to be editing on a machine with VBA7? does it also need to be VBA7/64 bit?

[ItsMe]

I really do not know because I do not use 64bit Office. I have been taking the wait and see approach. If your workgroup is hybrid 32 and 64 bit, the VBA that works for 32bit should work in the 64bit versions. There are a few exceptions where the code will not work.

What VBA code is not working in 64bit versions? Is it just around DLL files like, advapi32.dll?

If a machine is giving an error, search for the DLL file on the machine.

Use the VBA7 constant to determine the version of Access but, PtrSafe is not going to help if the DLL file does not exist in the system.

I would start there. Maybe look for an alternate method or a way to safely install the DLL. Does that DLL file exist on the machines running 64bit? Maybe it is a Windows Pro vs. Home or something.