Converting the 32-bit version of a code to 64-bit Versions

Hello,

I'm having some problems regarding the editing and making the code to compile successfully on 64-bit Versions

I've followed the differences of the code using the site here were each declaration can be saw on both version, but somehow the module will display an error about the different versions.
https://www.jkp-ads.com/articles/apideclarations.asp

Piece of code (also the entire document has been attached)

Please Login or Register  to view this content.

Is the Long vs LongPtr so important between versions? That's the problem?

ok, so I made the required changes to the code after reading every info I had about the x64 code. New one attached with a mismatch issue that i can't solve

If I recall correctly this mouse scroll issue was looked at in depth last year but I don't remember any satisfactory outcome being posted. I think in 64bit "one direction" scrolling was the furthest I saw it taken to....(hope i'm wrong but ??)

Changing the code for the 64bit, from Private hhkLowLevelMouse As Long to Private hhkLowLevelMouse As LongPtr results in the module will cause a new issue type mismatch at the line : LowLevelMouseProc = CallNextHookEx(0, nCode, wParam, ByVal lParam) and after a few seconds, excel will crash

i've tried that method but still the same issue is present.

Sure, added to the attachments with every test

Found the previous thread if it helps

https://www.excelforum.com/showthrea...89900#poststop

Originally Posted by rorya

You haven't done what I suggested at all in that workbook.

You should repeat all of the code inside each part of the conditional compilation clause. Then adjust the 64bit code section to use LongPtr for the variables and functions as necessary.

I have no idea what are you asking me to switch / move / replace can you submit a model?

Originally Posted by rorya

Completely untested.

Tested the file on a "faster" PC and after opening and trying to run the hook code, the excel instant closes without any warnings
On a low-end PC an automation error is displayed for 1-2 seconds then immediately closes

Originally Posted by rorya

Told you it was untested (I don't have 64bit here). Try this one.

I've never understood why people think this is worth it.

I know that the code was untested i just wanna provide as much info and clearance for you / others in order to try and pin - point the problem exactly.

As for the second idea : It's a nice feature to have on any available form that contains a large number of informations in a "tiny spot"

Regarding the last attachment, works like a charm, perfectly on any available device.

I reviewed the modifications you had made and i don't understand what or why or what the reason for spitting the code in 2 wide chucks / blocks of code separated by the excel version and why it didn't worked in the first place when the declarations were spitted in half (it's just for my personal knowledge )

Thank you.