I received a DLL from vendor in order to interface with device.
I asked vendor if my VB6 program is able to call this DLL but they have no idea about that because their engineer have never experienced VB6.
10 years ago, I have tried interface with DLL which was made by C language before several times.
When I open that DLL from Dependencies Walker, I could see total byte in the item of the function list like this.
1 (0x0001) 0 (0x0000) _BitNotOperation@4 0x00002070
But, in case of this new vendor's DLL, I could not see total byte like this.
1 (0x0001) 0 (0x0000) TRI_AcqImage 0x00005902
To figure out if this DLL is compatible with VB6 application, which one should I investigate from DLL? or what should I ask vendor?
FYI, I attached DLL/LIB/header file.
I asked vendor if my VB6 program is able to call this DLL but they have no idea about that because their engineer have never experienced VB6.
10 years ago, I have tried interface with DLL which was made by C language before several times.
When I open that DLL from Dependencies Walker, I could see total byte in the item of the function list like this.
1 (0x0001) 0 (0x0000) _BitNotOperation@4 0x00002070
But, in case of this new vendor's DLL, I could not see total byte like this.
1 (0x0001) 0 (0x0000) TRI_AcqImage 0x00005902
To figure out if this DLL is compatible with VB6 application, which one should I investigate from DLL? or what should I ask vendor?
FYI, I attached DLL/LIB/header file.