Certainly, there is no definitive "best version." I am simply curious about which office version is predominantly used and whether it its 32-bit or 64-bit.
I installed 32-bit because I prefer 32-bit Access and I installed Access with Office 2021 Pro package.
I have never worked with 64-bit version of any Office app.
I develop for operations in 2 cities. In one I have 32bit 2016, in the other I got forced on to O365 64bit. The 64bit conversion wasn't bad, but I hate being on the bleeding edge updates-wise. I've already been bitten by a couple of update related bugs.
I develop for operations in 2 cities. In one I have 32bit 2016, in the other I got forced on to O365 64bit. The 64bit conversion wasn't bad, but I hate being on the bleeding edge updates-wise. I've already been bitten by a couple of update related bugs.
Yes, i suggest most of us have been bitten more than once and the end client sometimes does not understand MS are at the forefront of the problem. We learn then to sandbox everything; turn all updates off for OS, Driver and Application Layer and keep an eye on the shit that follows before we consider and update lol
Some years ago we found that 64-bit versions would be a pain because of the fewer 64-bit .DLL (dynamic link library) files available. One issue is that 3rd-party providers built their offering on 32-bit machines and the 64-bit conversion either wasn't available or was a beta test. I have always stayed with 32-bit for any serious projects because of those 3rd-party issues.
I installed 32-bit because I prefer 32-bit Access and I installed Access with Office 2021 Pro package.
I have never worked with 64-bit version of any Office app.
I understand the 32bit approach and its my first choice for many reasons. I am concious however that my lack of knowledge forces me down this path hrystorically however im considering a new project soon and IF i choose Access for the project would like to think i can move away from 32bit and embrace 64bit completely.
I would have stayed with 32bit in the Vegas office but IT there went to O365 64bit for all the users, so I had to switch as well. I think it (the 64bit decision) was because of a few heavy Excel users, but I'm not really sure. As we all know it doesn't really benefit Access.
Some years ago we found that 64-bit versions would be a pain because of the fewer 64-bit .DLL (dynamic link library) files available. One issue is that 3rd-party providers built their offering on 32-bit machines and the 64-bit conversion either wasn't available or was a beta test. I have always stayed with 32-bit for any serious projects because of those 3rd-party issues.
Yes, me too.. I would like to think i could achieve what i require without making use of 3 party addons but i dont have the knowledge of Access & VBA. Without these 3rd party tools i honestly think this would limit me providing the simplicity to the end client.
I installed 32-bit because I prefer 32-bit Access and I installed Access with Office 2021 Pro package.
I have never worked with 64-bit version of any Office app.
I use both - need to because some clients have 64bit installed, others 32bit
but I still develop in 32bit 2010 (using ptrsafe, longptr etc as required) and test in 64 bit 365 when required. I'm expecting when I get a new pc (probably sometime this year) it will be the other way round. I do find 64bit (run on a virtual drive) is slow to load. Not sure if that is due to the virtual drive (which has 32gb memory) or 365.
I have been using both 32-bit & 64-bit since A2010 but with 32-bit as the default until last year.
I finally made the transition to 64-bit as the majority of my clients now use that.
If anything, 64-bit Access runs faster, particularly with memory intensive tasks
A VM will never give the same level of performance whether using 32-bit or 64-bit
I also now use A365 as my default dev version but create ACCDEs in both bitnesses ensuring they will run in A2010 upwards