isladogs
MVP / VIP
- Local time
- Today, 17:29
- Joined
- Jan 14, 2017
- Messages
- 18,186
To be fair @zeroaccess said 'after an update' and not 'after an upgrade'.
Upgrading to a new version (or bitness) of Access certainly breaks code for many reasons such as those stated and other reasons such as reference libraries or ActiveX controls that are no longer supported.
However running updates for the same version shouldn't break code ...though there have been too many cases where it does so.
For example, Access 2003 SP3 update and the hotfix that had to be rushed out, the update query bug in Nov 2019 and the recent A365 update 2004 for Apr 2020 which broke code linked to external sources.
However no update should change default settings applied by the end user
Upgrading to a new version (or bitness) of Access certainly breaks code for many reasons such as those stated and other reasons such as reference libraries or ActiveX controls that are no longer supported.
However running updates for the same version shouldn't break code ...though there have been too many cases where it does so.
For example, Access 2003 SP3 update and the hotfix that had to be rushed out, the update query bug in Nov 2019 and the recent A365 update 2004 for Apr 2020 which broke code linked to external sources.
However no update should change default settings applied by the end user