> What I haven't been able to do is QUIT 4D from within Active4D. I tried by > calling the command, and by calling our method that gracefully shuts down > but either cause the 4D Remote instance to hang w/ no response.
It probably hangs because it's in the middle of a web request. You'll have to add some kind of custom response header that you can look for in a post execute hook within 4D, then try quitting from there. >>> That code is -1. The only error code with that value is "A4D Not >>> Executable". >> >> That is a 4D error code, not an Active4D error code. > > In that case will it be possible to detect this in my custom error > handler? What will $a4d_err_type be? $a4d_err_type will be A4D Error Type Database, and $a4d_err_code should be -1. Regards, Aparajita _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
