Details

The 0.0.3.xx versions crashed unexpectively under not-so-well-defined circunstances. The program crash with an access violation error and sometimes with an error on a DAO dll. Also, sometimes it crashed with an EOSError (code 1400).

There were several problems with the 0.0.3.xx version of the module that are now fixed in 0.0.4.xx.

First, the critical sections were not defined globally. That caused unexpected access violations when accessing the VCL GUI components (which are not thread-safe).

Second, one parameter in three functions regarding a DAO table were not being passed by reference. That caused the DAO dll error, also in unexpected ways (some kind of queries triggered it, others did not).

The EOSError is caused by a thread referencing a VCL component (maybe GUI, maybe DAO) that no longer existed (because of the crashing). This error may appear again, as the module doesn't have still any termination-handling code. But as long as no crashing occurs, it won't happen (because the progran don't exit unless the last thread has terminated).