Point of sale Keyboard - exclusive use

[AndyGable]

This may not be a good idea. What if you need to perform some maintenance activities on the POS machine?

The best idea would be to see what is actually happening on the specific POS terminal. POS systems are prime targets for hackers, and the symptoms you are describing may be the result of a compromise on that PC. It could also be some sort of hardware issue or failure. An accurate diagnosis of the problem would be the best plan.

I can grantee 100% the till has not been hacked (it is not on any internet facing network) and for maintenance the system can be rebooted and a Admin user can log in and that account has all the standard functions working on the PoS

'**************************************
'Windows API/Global Declarations for :System Wide [ Global] Keyboard Hook - Pure VB
'**************************************
Public Declare Function CallNextHookEx Lib "user32" (ByVal hHook As Long, ByVal ncode As Long, ByVal wParam As Long, lParam As Any) As Long
Public Declare Function UnhookWindowsHookEx Lib "user32" (ByVal hHook As Long) As Long
Public Declare Function SetWindowsHook Lib "user32" Alias "SetWindowsHookA" (ByVal nFilterType As Long, ByVal pfnFilterProc As Long) As Long
Public Declare Function SetWindowsHookEx Lib "user32" Alias "SetWindowsHookExA" (ByVal idHook As Long, ByVal lpfn As Long, ByVal hmod As Long, ByVal dwThreadId As Long) As Long
Public Declare Sub CopyMemory Lib "kernel32" Alias "RtlMoveMemory" (Destination As Any, Source As Any, ByVal Length As Long)
Global Const WH_KEYBOARD_LL = 13
Public Const HC_ACTION = 0
Type HookStruct
vkCode As Long
scancode As Long
flags As Long
time As Long
dwExtraInfo As Long
End Type

I found the above while on google would anyone say that is the way to go?