32 bit database will not open with 64 bit version of Access

[Paul H]

I testing several databases that were built with the 32bit of Access on machines that are using the 64 bit of Access and am getting a couple different errors.

For this one the database won't open under any circumstances


This one opened, but the start up form won't display. I was able to get to the form and open it manually. When I did I received this error. By commenting the code in red the form opened normally, but I am unsure what this code does


I also found these two sub that call the above functions.


Your thoughts on either or both of these would be appreciated.



Thanks,

Paul

[Mickjav]

Database will only work in the version they are complied In
And you need to update you API Calls to use PtrSafe and LongPtr
http://allapi.mentalis.org/apilist/apilist.php
https://www.utteraccess.com/wiki/Category:API

[pbaldy]

Also, in my experience an accdb created by 32bit Access will open fine in 64bit. An accde created by 32bit Access will not, and you get the first error. I've opened numerous 32bit accdb's in 64bit; you have to in order to convert them.

[Paul H]

Also, in my experience an accdb created by 32bit Access will open fine in 64bit. An accde created by 32bit Access will not, and you get the first error. I've opened numerous 32bit accdb's in 64bit; you have to in order to convert them.

I have some accdbs that have opened up without errors. So far two others haven't. I've taken one and imported all the objects into a 64 bit Access database, but Function declarations still produce this error. This is occurring in both dbs but I am unfamiliar with this code and not sure how to update it.



Here are the instances where that happens. If I can get through these I might be in the clear.

Declare Function GetSystemMetrics32 Lib "User32" _
    Alias "GetSystemMetrics" (ByVal nIndex As Long) As Long

Public Declare Function SHAppBarMessage Lib "shell32.dll" (ByVal dwMessage As Long, pData As APPBARDATA) As Long

Declare Function SetWindowLong Lib "user64" Alias "SetWindowLongA" _
    (ByVal hwnd As Long, _
    ByVal nIndex As Long, _
    ByVal dwNewLong As Long) As Long

Public Declare Function CallWindowProc Lib "user32" Alias "CallWindowProcA" _
    (ByVal lpPrevWndFunc As Long, _
     ByVal hwnd As Long, _
     ByVal msg As Long, _
     ByVal wParam As Long, _
     ByVal lParam As Long) As Long

[pbaldy]

Mickjav covered that in post 2. In simplest terms

Declare Function...

becomes

Declare PtrSafe Function...

But it can get more complicated, so review the links posted.

[Paul H]

I did a google search and found a template I could use. I tried using my old code in the else section, but it still kicked out the same error. At this point it is running on both the 32 bit and 64 bit versions of Access, which I didn't expect. I've got one other database to debug. I expect this to work there too.

Thanks for helping out.

Paul

#If VBA7 Then
    Declare PtrSafe Function SetWindowLong Lib "user64" Alias "SetWindowLongA" _
    (ByVal hwnd As LongPtr, _
    ByVal nIndex As LongPtr, _
    ByVal dwNewLong As LongPtr) As LongPtr


#Else


 '   Private Declare Sub Sleep Lib "kernel32" (ByVal ms as Long)
#End If

#If VBA7 Then


Public Declare PtrSafe Function CallWindowProc Lib "user32" Alias "CallWindowProcA" _
    (ByVal lpPrevWndFunc As LongPtr, _
     ByVal hwnd As LongPtr, _
     ByVal msg As LongPtr, _
     ByVal wParam As LongPtr, _
     ByVal lParam As LongPtr) As LongPtr

#Else

'The old code would not work here
#End If

[Mickjav]

nIndex
msg
dwNewLong
As LongPtr

Think these should all be longs

[Paul H]

I'm not surprised, but there is more to this. While the application runs normally, I can no longer compile it. I am getting type mismatch errors on this line of code.

Public Function UpDateRptRecPgmOR(RptRec As ADODB.Recordset, Qtr, provider_ID, Nclient) As Boolean
Dim i As Integer
        
    RptRec.MoveFirst
    For i = 1 To RptRec.RecordCount - 1
      If RptRec("Quarter") = Qtr And RptRec("Provider_Id") = CInt(provider_ID) Then
          Exit For
      Else
          RptRec.MoveNext
      End If
    Next i
    
     RptRec("Program_ORs") = Nclient
     RptRec.Update
     
    End Function

This happens on two other functions. There are no longs in these functions. I checked the links, but didn't see anything related. I altered this line of code till the code compiled, but I need a real solution.

From this

    For i = 1 To RptRec.RecordCount - 1 

'

to

For i = 1 To 2 'RptRec.RecordCount - 1

[Mickjav]

Your gettng the errors as your not using LongPtr correctly read up up 64 bit api calls

[isladogs]

Rather than react to each error without a clear understanding of API conversions, I suggest you research the correct approach
The following should help
1. Read the article by Phillip Stiefel at https://codekabinett.com/rdumps.php?...ion-vba-64-bit
2. download the Windows API Viewer by Ron de Bruin from https://www.rondebruin.nl/win/dennis...sapiviewer.htm
That includes both 32-bit and 64-bit versions of most APIs.

As well as adding PtrSafe for all 64-bit declarations you must convert pointers/handles such as hWnd to LongPtr.
Don't forget to review those in Type code blocks

[Paul H]

I did some research and fixed my declarations on my own. While I did not see any other Longs in the code, after some experimentation I changed the Integer data type to LongPtr and solved the problem.

I still don't know what an API is, but I guess it doesn't matter.

[isladogs]

I did some research and fixed my declarations on my own. While I did not see any other Longs in the code, after some experimentation I changed the Integer data type to LongPtr and solved the problem.

I still don't know what an API is, but I guess it doesn't matter.

I've no idea which API contains the Integer datatype you are talking about but converting that to LongPtr is completely wrong.
As I said before, if you are going to convert databases to 64-bit, you need to do it properly
Even if you've now managed to compile your database(s), it doesn't mean the APIs will now work correctly

[June7]

Bing "API definition".

Application Programming Interface

"In the simplest terms, APIs are sets of requirements that govern how one application can talk to another. APIs aren’t at all new; whenever you use a desktop or laptop, APIs are what make it possible to move information between programs—for instance, by cutting and pasting a snippet of a LibreOffice document into an Excel spreadsheet."

The API code referenced in this thread is for Windows/Access interaction.

[Paul H]

I've no idea which API contains the Integer datatype you are talking about but converting that to LongPtr is completely wrong.
As I said before, if you are going to convert databases to 64-bit, you need to do it properly
Even if you've now managed to compile your database(s), it doesn't mean the APIs will now work correctly

I'm not sure this is related to an API, but this is what prevented the db from compiling. The error I received was Datatype Mismatch.

Public Function UpDateRptRecPgmOR(RptRec As ADODB.Recordset, Qtr, provider_ID, Nclient) As Boolean

Dim i As Integer
        
    RptRec.MoveFirst
    For i = 1 To RptRec.RecordCount - 1
      If RptRec("Quarter") = Qtr And RptRec("Provider_Id") = CInt(provider_ID) Then
          Exit For
      Else
          RptRec.MoveNext
      End If
    Next i
    
     RptRec("Program_ORs") = Nclient
     RptRec.Update
     
    End Function

Public Function UpDateRptRecPgmOR(RptRec As ADODB.Recordset, Qtr, provider_ID, Nclient) As Boolean

Dim i As LongPtr
        
    RptRec.MoveFirst
    For i = 1 To RptRec.RecordCount - 1
      If RptRec("Quarter") = Qtr And RptRec("Provider_Id") = CInt(provider_ID) Then
          Exit For
      Else
          RptRec.MoveNext
      End If
    Next i

     RptRec("Program_ORs") = Nclient
     RptRec.Update
     
    End Function

I'm not receiving any errors in the application. It's compiled and converted to an ACCDE and working normally. I'm not sure there is anything left to fix.

[isladogs]

Nothing to do with an API.

Integer is fine for record count providing the count doesn't exceed integer limit (32767 IIRC).
I normally use Long for that reason. LongPtr is incorrect even if it compiled

If I starts at 1. and ends with RecCount -1, the final record will be excluded
Normally start at zero or remove the final -1.