Jörg Hi Jorg - here's the timeline.

2/13 I contacted support with a description of my issue

2/13 support replied they had restarted my workspaces and to try again

2/13 I replied  the problem persisted

2/16 I contacted support again, sending a copy of my database

2/17 Support contacted me asking me to "Confirm whether your database uses the sendEmail function anywhere? Also, have you recently edited or added a new sendEmailfunction before creating the archive (for example in version 3.05)? If so, that could potentially be causing the issue when reopening the database.

2/17 I replied that I do use that function, that it had been in place for weeks without causing any issue. I also explained i had tried to import 5 previous versions into each of my workspaces with the same failure each time. Several of these versions were before I built the sendEmail scripts.

2/18 Support emailed me that they were able to import my DB into their local Mac app successfully and that I should try that. he also said the issue had been identified by development and they were working on it. He suggested I use the mac app as my test platform in the meantime.

2/18 I responded, thanking him fort the update but let him know that a few of my functioning online scripts don't run in the local Mac app, so that approach really was not viable. I asked if there was a way to make a copy of my production DB in either of my online workspaces, which would let me designate one as a test platform.

That was my last communication from Support. I decided soon after that to load my most recent online backup file into the production workspace and rename that file as my test platform, which as been working fine for a couple of days. But no, i was not notified that the problem was resolved.