I have a MS Access 2003 application that was compiled on Windows XP to create the.exe file. The application appears to run correctly in all areas except when entering numeric data with my numeric keypad. With the NUMLOCK on, sometimes the #3 key or the#9 key functions as a Pg Dn or a Pg Up. Has anyone else experienced this? I am using the Access 2003 runtime.
Microsoft Access Runtime Downloads. What is Access Runtime? Microsoft Access Runtime is a free version of Access that allows you to run Access applications including entering, deleting and modifying records. It does not have any of the development and design tools of a full version of Access so you cannot make any changes to the design of an. Access runtime 2003 will not start on Windows 10 (Enterprise). Using an.msi package I can successfully install Access 2003 runtime. However, when I start Access with Northwind it crashes before displaying the database. If I start Access without a database it crashes before it reaches the 'You have forgotten your database'.
I do not have the ability to recompile the application using Access 2003 on Windows 10 nor do I have the time to recompile and work thru issuesby recompiling source code under Access 2013. Any thoughts or ideas would be greatly appreciated.Mike Bromley. First, you cannot 'compile' an Access application to create an EXE file. If you have an EXE file then the front end, at least, was NOT developed using Access.Second, assuming you have an MDE file, not an EXE, then the issue may have something to do with your keyboard or the way Win 10 is reading your keyboards.
I do not believe that Access 2003 uses UNICODE so that could be the issue.The only thing I can suggest would be to try running the app under the 2010 (or later) Runtime and see if that fixes the problem.However, If you do not have the original MDB file or cannot get it, then I would start thinking of rebuilding your application. The likelihood is that other things will start breaking or not work properly. I just encountered an instance in one of my appsoriginally developed in Access XP, but upgraded to an ACCDB. Code that was originally written for Access XP/Win XP all of a sudden stopped working.
I rewrote the code basically only changing the way objects were referenced and now its working fine. The moralis that older code may not continue to work.Hope this helps, Scott Blog: Microsoft Access MVP since 2007.
I still have the issue with the Logitech wireless keyboard. I have found a workaround as this only affects the computers that use the Access application and have Windows 10 and have ths wireless keyboard. I did do some minor searching on the Logitech supportsite for a driver download but ran out of time. I intend to pursue this and I will update this post once I have determined if a new driver fixes the problem. Clearly, this is NOT and Access issue whatsoever as I initially thought.Mike B.