I am working with a client app developed in Access 2003. Eventually we will be converting the app to run in Access 2013.
I have several machines in the office with different version of Access and different operating systems. There is a very long running 'Aging' process in the application being converted. It runs thru all of the entries in the DB and ages the accounts at the threshold of a new month, adding any new interest, penalties and fees due as of the new month.
Out of curiosity I ran the process on three different machines in the office. At this point the application (both the front end and data_ are in MDB format. The backend/data MDB is about 1GB in size.
In all cases the app was run 'locally' meaning the front end and data were in the same directory on C: drive of the machine.
All machines have the full version of Access installed.
Machine 1: Win 7 Pro, Access 2010, i7 processor 16GB memory.
The process ran 1hr and 17 minutes. I ran it multiple times, all times were within a minute or two of 1:17.
Machine 2: Win 8 Pro, Access 2010, i7 processor 32GB memory.
In multiple test the processing time were very close to the time on machine 1, 1:17 - 1:20.
Machine 7: Win 7 Pro, Access 2013, i7 processor 24GB memory.
In multiple tests the processing time was about 10 hours, or 7.5 times longer than either of the other machines.
I have run these tests multiple times on each machine with pretty close, within minutes, to the same result. At one point I even upgraded the app from MDB's to Accdb's using the 2013 'save as'. I de-compiled the app and recompiled it in 2013 and ran it on both Machine 3 (2013) and Machine 2 (2010). Machine 3 was still in the 1:20 range, Machine 1 was still in the 10 hour range.
One thought I had was that maybe Access 2013 was 64 bit version but it shows 32 bit on the 'About' screen. The version of Office Professional 2013 was installed from a download and activated with a keycard. Both 2010 versions were installed from an install CD for Office 2010 professional
Why is the 2013 execution drastically slower? This is exactly the same code, run in exactly the same way, the only difference being machine 3 has Access 2013 installed. Machine 3 has more memory and a faster processor than Machine 1. I find this very disturbing and have no explanation.
Does anyone have any ideas or experienced similar results and hopefully have a solution?
I won't be able to upload the app or the data due to sensitive content.