Addin Issue Creating an N when opening a workbook on the Sheet

[mayoung]

I have been using an addin I created for some time. Recently I have noticed when I open an excel workbook and the addin opens it adds the letter N randomly onto the excel worksheet I have opened and its never to the same cell. If I uncheck the addin and close my workbook and reopen it this no longer happens. I thought maybe the addin workbook got corrupted so I open another workbook and moved all the modules over to it and resaved it as my addin. Then I moved my xml code using the ribbon editor. The letter N still appears randomly. Can anyone offer any suggestions??

 

[mayoung]

Do you want to load a copy without the password or send the password ?

There is no password to open the code?
Or what password do you mean?

 

[Alex Blakenburg]

Sorry that was a different XLAM. I can't replicate the issue you are having and I can't see anything in the code that could cause it.
(PS: I had to modify Module120 to make it work on my 64 bit installation)

Is there any chance that you have other Personal Macros or Add-Ins running that might be interacting with this one ?
If you have maybe disable them and leave this one turned on to see if it is actually the combination that is causing the issue rather than this one on its own.

 

[mayoung]

Sorry that was a different XLAM. I can't replicate the issue you are having and I can't see anything in the code that could cause it.
(PS: I had to modify Module120 to make it work on my 64 bit installation)

Is there any chance that you have other Personal Macros or Add-Ins running that might be interacting with this one ?
If you have maybe disable them and leave this one turned on to see if it is actually the combination that is causing the issue rather than this one on its own.

That is the only addin I have checked off that should be running. Kinda of strange what it is doing.

 

[Alex Blakenburg]

Sorry I wasn't able to resolve it for you.

 

[Peter_SSs]

I can't replicate the issue you are having and I can't see anything in the code that could cause it.

Same for me.

 

[mayoung]

Sorry I wasn't able to resolve it for you.

Thank You for looking at it.

 

[mayoung]

Same for me.

Thank you for looking at it

 

[Alex Blakenburg]

I had to modify Module120 to make it work on my 64 bit installation

Regarding the above. I added the word PtrSafe to the following in Module120

' API declarations:
Private Declare PtrSafe Function GetVersionEx Lib "Kernel32" _
                                      Alias "GetVersionExA" _
                                      (lpVersionInformation As OSVERSIONINFO) As Long

Private Declare PtrSafe Sub keybd_event Lib "user32" _
                                (ByVal bVk As Byte, _
                                 ByVal bScan As Byte, _
                                 ByVal dwflags As Long, ByVal dwExtraInfo As Long)

Private Declare PtrSafe Function GetKeyboardState Lib "user32" _
                                          (pbKeyState As Byte) As Long

Private Declare PtrSafe Function SetKeyboardState Lib "user32" _
                                          (lppbKeyState As Byte) As Long