Blocking error with access violation using Firedac sql monitor in uniGUI
I set up a Firedac connection and a FDMoniFlatFileClientLink for each uniGui session. In the firedac connection I added the parameter 'MonitorBy=FlatFile'. I then configured FDMoniFlatFileClientLink to generate a log file whose filename depends on the session id. When starting the first session it works correctly, if I launch a new session the uniGui application crashes and generates the access violation error. How can I solve the problem? Is there a best practices and a demo for using a firedac
I answer for information (for everyone):
It will work if -
For each session, create a separate monitor instance(example in mainmodule)(a unique log file) (for connections used by this session).
Create connection:
1. If you are trying to create a single pool of connections (fd, unidac - the pool code already has synchronization methods) per process, then you need to unbind the connections from the owner Connection.Create(nil) and control the life cycle of connections and depe