23-07-2019, 03:38 PM
It's seems to be a timing issue - if not all ActiveX controls are destroyed correctly it runs into that error - we can reproduce - and we implement a short "delay" to prevent this error with the next patch
Regards/Gruss
Oliver
Oliver