But then again, if your virtilizing app's and installing a whole truck load of external dependence, then that defeats the whole goal here. However, as we cross this bridge and transition to this zero installing day, we see that 2013 (and I think 2016) did install + use a virtilized app version of Office/Access, but also for the transition did install a set of stubs thatĪre outside of the virtilized app,and this was to facilitate external programs using ACE.
(they are moving towards the day when in fact you don't even install Access - it will be a single. Regardless, just keep in mind that CTR installs now don't registrar and expose the ACE engine by default. And you ALSO cannot mix and match the x32 bit versions of office with 圆4 - butĪgain ONLY for the same version of office.
What you can't do is mix and match the same version of office between MSI and CTR installes. The short issue and story is simply that with Access 2019 (and 2016) CTR (click to run - which is most installations,then installing Access does not expose a registered copy of ACE).Īnd no, you are not prevented from installing previous versions of office. The office installs (programs) are now virtulized applications.
