BullZip Home

I have been using msa2mys for years to export data from a MS Access .mdb to a .sql dump file (biweekly). It has been working fine until (and including) June 23rd, but failed on July 9th. It hangs on collecting the tables/columns names (shows an blank window where the tables should be listed).

I am on Windows 10 Pro 64-bit, still on 2004 (update for 21H1 is available). My system locale is Dutch/Netherlands. I use ESET Internet Security.

As far as I know, I have not changed anything in the meantime. The following things have changed automatically:
- June 26th: preview version of cumulative update for .NET Framework 3.5 and 4.8 (KB003537)
- July <6th: update for Microsoft 365-apps for businesses (from 16.0.14026.20270 to 16.0.14026.20308)
- July 7th: update for Microsoft 365-apps for businesses (from 16.0.14026.20308 to 16.0.14131.20278)
- July 7th: cumulative update for Windows 10 version 2004 for x64 based systems (KB004945)
- ESET Internet Security (was updated in that period from 14.1.20.0 to 14.2.19.0)

System recovery only shows a recovery point on July 11th. I have created a new recovery point, and am planning to:
- upgrade msa2mys from 5.4.0.274 to 5.5.0.282 --> no improvement
- try it on another .mdb (also on a old one without opening it in MS Access first) --> no improvement
- downgrade Microsoft 365-apps for businesses (to 16.0.14026.20308 released June 18th and even to 16.0.14026.20270 released June 8th)
- remove KB003537
- remove KB004945
- upgrade Win10 from 2004 to 21H1

I will report the results here. In the meantime, any other suggestions?

Oh wow, switching back to 16.0.14026.2038 solved the problem! I found useful instructions here: https://support.microsoft.com/en-us/top ... 09e3dda841

I hope the Bullzip team can update msa2mys so that we can allow future MS Office updates (to 16.0.14131.20278 and beyond).