This may be a dumb question as I am not sure why or how this worked before today.
Up until today, whenever 4D encountered any kind of error in my code while handling an HTTP request the code was immediately aborted and my web app got a response that included the method name, line number and error description. Like I said, I do not know why it did that, but I liked it as I could detect the error in my web app and throw up a message box telling me what was wrong. All of a sudden 4D just keeps on going. For example, test=test on a line all by itself will in a normal process throw an error. Before today In a web process it would terminate the process and send back the error. Now the web app no longer gets the error. What it does get back depends on how the error affected my xml response. If I put a TRACE before test=test 4D honors the TRACE, but just keeps on trucking after I tell it to continue. If I put the TRACE after test=test, the TRACE is ignored and the web app gets back whatever my later code is able to send back. I didn’t change anything. Any ideas? John ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
