Noticeably degraded same code performance with later Access versions (1 Viewer)

[amorosik]

Converting an old project born under Access 2003 to Access 2013 I'm noticing a deterioration in performance on various document creation procedures
A document export that used to take 40 seconds now takes about twice as long, same code, same database, only runtime Access2013 intead Access2003
Is this kind of performance degradation possible?

 

[gemma-the-husky]

Newer versions of Access tend to require a more powerful PC. If you have barely enough memory and resources, it could be that an older version performs better. It may be something else, but this is a possibility. It's rather like bloatware.

Sorry these aren't from the same source, but you can see the A2013 system is is hungrier

A2013 access 2013 system requirements - Search (bing.com)
Minimum System Requirements - Microsoft® Office Access 2003 Step by Step [Book] (oreilly.com)

 

[ebs17]

Is this kind of performance degradation possible?

Naturally. There was a change to XML-basedness with Access 2007, and the Ms Access development team is limited in numbers alone.

A document export that used to take 40 seconds

For many, that would be unacceptably bad. Reason enough to start looking for weaknesses and problems not only in others, but to start an analysis of yourself and your own designs.

Because: core functionalities such as the original VBA and SQL have practically not changed at all since Access 2000, minor changes there certainly do not cause any loss of performance.