![]() Rather than the monthly updates with 365. So I've already had the version you are using without any issues. Rather than the monthly updates with have a slightly newer version of A365 than you: 8.20334 (32-bit) which is A365 version 2010 (Oct 2020 update). The point about newer versions of Access being less tolerant of code that would have been acceptable in older versions is well documented. Having said that recent versions of Access should delete any such empty code procedures. For example do you have any 'empty' code procedures - header & footer line only with nothing between. In addition, ACCDE creation can fail for a number of reasons. If your error handling is not sufficiently robust, code can fail in an ACCDE that works in an ACCDB. and yes I remember the query is corrupt issue only too well as well as other similarly catastrophic bugs both recently and even back as far as Access 2003 SP3. I see no evidence that there is a bug in the Make ACCDE process. Most of these contain more than 4 VBA references. I have made multiple ACCDEs over the past few months and again today. Have a slightly newer version of A365 than you: 8.20334 (32-bit) which is A365 version 2010 (Oct 2020 update).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |