- #Deactivate virtual keyboard windows 10 how to#
- #Deactivate virtual keyboard windows 10 windows 10#
- #Deactivate virtual keyboard windows 10 pro#
UAC comes up, click yes, same error ('Could not start On-Screen keyboard'). ShellExecute 0, "runas", "C:\windows\system32\osk.exe", "", "", SW_SHOWNORMAL Then, enabled the administrator account and logged on as administrator.
#Deactivate virtual keyboard windows 10 pro#
I have tried opening Access (2013) as administrator (on both a Surface Pro 3 and a laptop). That involved Access/ODBC/SQL Server - which (BTW) has never been fixed. I was told this, flat out, several years ago during a support incident IMHO, there is still not enough communication between the various teams. I'm sure no one set out to create the issue and the fault lies with Microsoft and not with the teams. I do understand that this is a Windows issue, I posted here because I'm working in Access and don't know of anywhere else to post where I'm likely to get a response from anyone connected to Microsoft. Datasheets actually respond quite well to swipe action.
We would be happy (for now) with keyboard action. Thanks for responding, Shane, I certainly appreciate your time - and taking the brunt of my frustration :).įull touch capability would be awesome, however, I (as well as end users) do understand that it would be a major change. Thanks for letting us know about the issue, and we'll let you know if we have any updates for you.
#Deactivate virtual keyboard windows 10 windows 10#
I mentioned tabtip.exe because it is the keyboard that will come up when you use a touch-enabled app on Windows 10 (rather than osk.exe) Are you logged in as an Adminstrator? If not, can you try that and see if it works in that case (I know this isn't a workaround, just trying to isolate the issue). I'm not sure why you are still getting the error after the UAC prompt. Use case for the on screen keyboard (using it with older applications with no built-in support). Space, I was just trying to help out in the meantime.Īs far as taking away ways to launch the on-screen keyboard, that is something completely outside the scope of Access, and I don't think the Windows team set out to make things more difficult for anyone, but they may not have considered this the primary However, we recognize that touch is pretty common now, so we are looking at what we can do in this lpDirectory = "C:\windows\system32" 'best to use Known folders hereĬall Wow64DisableWow64FsRedirection(lngPtr)Ĭall Wow64RevertWow64FsRedirection (lngPtr)Īccess was around before ubiquitous touch screens, so it wasn't added initially, and we try to prioritize appropriately when adding new functionality. To work on a Surface, required 2 additional API's.ĭeclare Function Wow64DisableWow64FsRedirection Lib "kernel32.dll" (ByRef ptr As Long) As Booleanĭeclare Function Wow64RevertWow64FsRedirection Lib "kernel32.dll" (ByRef ptr As Long) As BooleanĬall Wow64DisableWow64FsRedirection prior to calling ShellExecuteEx and Wow64RevertWow64FsRedirection, immediately after. This, however, did not work on a Surface Pro (3 or 4). '.fMask = ShellExMask.SEE_MASK_INVOKEIDLIST 'or ShellExMask.SEE_MASK_NO_CONSOLE 'tried using masks, but they either had no effect or crashed Access lpDirectory = "C:\windows\system32" 'best to use Known folders here lpFile = "C:\Windows\Sysnative\cmd.exe" 'best to use Known folders here Public Declare Function ShellExecuteEx Lib "shell32.dll" _ The first is just using ShellExecuteEx and worked fine on my Laptop. Here is the solution arrived at from my Microsoft support case.
#Deactivate virtual keyboard windows 10 how to#
I have googled for hours and not found anything else.Īnyone have any other ideas how to open the on screen keyboard via VBA? Opening osk.exe DOES work directly from the command line, Windows run box, Windows Explorer, bat file or shortcut. Same results using C:\Windows\SysWOW64\osk.exe Results in vba error 'Invalid Procedure call'Ĭreate bat file to open osk.exe and call the bat file via shell or ShellExecuteĬreate Shortcut to open osk.exe and call the shortcut via shell or ShellExecute The message is not a vba error, it is from the exe.ĪpiShellExecute 0, vbNullString, "osk.exe", vbNullString, "C:\Windows\System32", 1 Instead there is a message 'Could not start On-Screen keyboard' However, that no longer works in Windows 10. In Windows 8, the workaround was a shell call to osk.exe, and the on screen keyboard would open.
Access 2013 32bit application running Windows 10 Pro on a touch device (laptop or touchpad).Īs we all know, the on screen keyboard does not open when tapping a textbox in Access.