![]() You have already done what I would have recommended, and that is to import your old objects into a new, blank DB. We had very few issues with the new 64 bit machines. We recently did our upgrade to 64-bit machines/Software here at work, too (government is always slow, due to validating security issues with new systems/software). I am a bit afraid of unknown compatibility issues, but likes what appears to be a bit more speed with the 64 bit version.Ĭan anyone share their experiences with 64 bit upgrades? Better to upgrade to 64 bit or stay at 32 bit? Some comment on the Internet suggests that it is better to keep the 32 bit version, and avoid compatibility issues. This mostly works, though I noticed some errors (problems with code translation to 64 bit ?). For the 64 bit version, one needs to create a 64 bit blank database, and import all the 32 bit objects into the blank data base. Our existing MS Access code runs completely (it appears) without problem on the 32 bit version of MS Access 2016 (32 bit). We thus decided to upgrade to MS Access 2016.įull disclosure: Never realised there was 32 vs 64 bit Versions of MS Access. They were running MS Access 2007, which is no longer supported by Microsoft. We have about 7 machines on a front end back end configuration running off our mighty (cheap) WDM圜loud "server". I volunteer coding MS Access for a food bank in Aylmer, Quebec.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |