

I rewrote the code basically only changing the way objects were referenced and now its working fine. Code that was originally written for Access XP/Win XP all of a sudden stopped working. I just encountered an instance in one of my apps originally developed in Access XP, but upgraded to an ACCDB. The likelihood is that other things will start breaking or not work properly.

However, If you do not have the original MDB file or cannot get it, then I would start thinking of rebuilding your application.

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. I do not believe that Access 2003 uses UNICODE so that could be the issue. 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. If you have an EXE file then the front end, at least, was NOT developed using Access. The software installer includes 35 files and is usually about 559.33 KB (572,751 bytes).įirst, you cannot 'compile' an Access application to create an EXE file. The main program executable is accicons.exe. 0, with over 98% of all installations currently using this version. Microsoft Office Access 2003 Runtime is a program developed by Microsoft.
