As mentioned in help:

• Longptr

  In the 32-bit platform, longptr is the same as long; you can continue using long wherever longptr is required in 32-bit applications. In 64-bit applications, however, using long to hold longptr variables will lead to data truncation from 8 bytes to 4 bytes, or memory corruption if you pass a long ref variable when a longptr ref is required. If you want to migrate to 64-bit, use longptr wherever required as it does no harm to 32-bit.

  Since PowerBuilder does not have a datatype corresponding to the C++ pointer type, and there are no pointer operations in PowerBuilder, longptr is not a full-fledged PowerBuilder datatype. You can use it to hold/pass window handles, database handles, and other objects that are essentially memory addresses. Doing complex operations on longptr type might not work. If you want to represent/compute 8-byte long integers, use longlong.

• LongLong

  To take advantage of the 64-bit architecture, you can change your Long datatype variables to LongLong. Because this datatype is for 64-bit signed integers, from -9223372036854775808 to 9223372036854775807.

  Keep in mind that LongLong continues using literals as for integers, but longer numbers are permitted.

You can find this on the following link: Step 2 - Datatypes - - Migrating 32-bit Applications to 64-bit (appeon.com).

Some methods from odbc32.dll are used to pass handles, so I guess you have to use longptr or longlong. You should modify your declarations and test again.

Andreas.