[AccessD] 32->64 bit

Stuart McLachlan stuart at lexacorp.com.pg
Mon Nov 8 17:15:27 CST 2021

On 9 Nov 2021 at 9:02, Borge Hansen wrote:

> So your task may go something like this (with a repeat and rinse many
> times): Search for Lib "User32" - restrict to one module at a time so
> you have an idea which modules you've covered...

Danger, Will Robinson!

The WIn32 API uses a lot more than User32 !

Here's a few extracted from one old .MDB:

Declare Function GetUserName Lib "advapi32.dll" Alias "GetUserNameA" (ByVal lpBuffer 
As String, nSize As Long) As Long
Private Declare Function GetTempPath Lib "kernel32" Alias "GetTempPathA" _
 (ByVal nBufferLength As Long, ByVal lpBuffer As String) As Long
Private Declare Function SHGetSpecialFolderLocation _
    Lib "shell32" (ByVal hwnd As Long, _
    ByVal nFolder As Long, ppidl As Long) As Long
Private Declare Sub CoTaskMemFree Lib "ole32" (ByVal pvoid As Long)
Declare Function GetOpenFileName Lib "comdlg32.dll" Alias _
         "GetOpenFileNameA" (pOpenfilename As OPENFILENAME) As Long

That's 5 different API Libraries (Lib"s)

It's easier ust to  look for at the "DECLARE"  lines at the top of each module

As MS puts it: Declarative statements must appear before the first procedure declaration.

More information about the AccessD mailing list