It actually was being called. The A4D method calls a 4D method. The problem was in the 4D method. Tracing that method verified A4D was being called.
I had placed write to console calls in Active4D before and after calling that 4D method. I wasn't seeing any prior expected write to console output and assume (falsely) that the script was not running. Thanks, Brad On 11/20/14 12:32 PM, "Aparajita Fishman" <[email protected]> wrote: >> Can anyone provide any debugging suggestions? > >- Put a trace in A4D_OnWebConnection (or the NTK equivalent) before the >call to Active4D. >- Post the text from the remote application. >- If the trace is not reached, then 4D is eating the request. >- If the trace is reached, see what the status and response is. > >Regards, > > Aparajita > >_______________________________________________ >Active4D-dev mailing list >[email protected] >http://list.aparajitaworld.com/listinfo/active4d-dev >Archives: http://active4d-nabble.aparajitaworld.com/ > _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
