I can’t do anything about the availability of third-party-components, so in this article, I’m going to focus on the migration of Win-API calls in VBA to 64-bit compatibility. – It is not possible to mix and match 32- and 64-bit applications from the Microsoft Office suite. So, whether you as an Access developer like it or not, you might be confronted with the 64-bit edition of Microsoft Access because someone in your or your client’s organization decided they will install the whole Office Suite in 64-bit. financial risk calculations, you will probably benefit from the additional memory available to a 64-bit application. If you use Excel to calculate large data models, e.g. For Excel, there actually are use cases for the 64-Bit edition. Unfortunately (in this regard) Access is part of the Office Suite as is Microsoft Excel. The basic problem exists with 64-bit Access as well, but it takes much longer until you will see any memory related error. When you open multiple forms at the same time that contain a large number of sub-forms, most likely on a tab control, you might run into out-of-memory-errors on 32-bit systems. There is only one benefit of 64-bit Access I’m aware of. And finally, Access applications using the Windows API in their VBA code will require some migration work to function properly in an 圆4-environment.Only if you need to connect to some old legacy systems this might still be a factor. – Though this should rarely be an issue nowadays. Drivers/Connectors for external systems like ODBC-Databases and special hardware might not be available.Yes, this is still a problem in 2017, more than 10 years after the first 64Bit Windows operating system was released.
0 kommentar(er)
