Thomas E. Davis wrote: > > Essentially the error message gets written to the trace listeners before being > trapped by the Try...Catch block in which the database access attempt is nested. >
I'm not sure which error message you are referring to? Could you provide the text of the error message? > > It isn't a huge issue because the exception/error does get trapped and processed > in accordance with my handler block but I would prefer not to have the error > presented in the trace output before being trapped/processed. > What code is raising an exception? What kind of exception is being raised? > > It appears to me that all other exception/error paths get caught and processed > as expected. > Which code are you referring to? -- Joe Mistachkin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
