Furhter analysis has shown that what hangs the system is the first query to
the 4D database from within the "On Session End" method.


I don't know why that hangs in client/server mode, but it is a fact. It
seems that the client does not receive an answer from the process started on
4D server that handles the database request.


It does work just fine in 4D standalone but hangs the 4D Client in client
server mode.

I have verified this problem, and it is a 4D bug. But I have a new beta version that fixes this by spawning a new process in the shell and then calling into the Active4D housekeeper from that process. That way the process is global and queries work as expected on Client.


If you are absolutely in need of this, let me know, I will make it available.

Regards,

   Aparajita
   Victory-Heart Productions
   [EMAIL PROTECTED]
   www.aparajitaworld.com

   "If you dare to fail, you are bound to succeed."
   - Sri Chinmoy   |   www.srichinmoylibrary.com




Reply via email to