Before I waste time chasing errors in macros that work perfectly well on W10 PCs but fail with unhelpful error codes on Mac, can anyone tell me if UNO commands in macros running on Big Sur have been extensively tested, or am I in uncharted territory?
I have a database running in 220.127.116.11 LO, HSQLDB embedded, including several macros in Basic which work fine on an Intel Core 7 powered PC running Windows10. When this same .odb is run on a Macbook Pro M1 running Big Sur, the macro code fails on some lines of code like “Set oFS = CreateObject(“Scripting.FileSystemObject”)” or “Stmt.executeUpdate(strSQL)”.
In the latter case, LO crashes and has to be forcibly killed to regain control. I upgraded LO to 7.1 on the Mac to see if it made any difference - it doesn’t.
Has anyone else seen such behaviour? If so, how did they get around the problem?
Thank you in anticipation of some helpful advice.