If you’re using SQLitePreparedStatement for optimum efficiency (rather than using the implicit prepared statements offered by API 2), those don’t execute as API 2. This means they don’t raise exceptions. You would need to check SQLiteDatabase.Error, SQLiteDatabase.ErrorCode, and SQLiteDatabase.ErrorMessage.
Source: I just tested this.
Try not to make too much noise about this issue, those of us who understand why / when you should use SQLitePreparedStatement do not want the feature being removed. Xojo has made some very short sighted decisions with SQLite changes recently.