On Nov 07, 2006, at 10:08 PM, Charles Yeomans wrote:
On Nov 7, 2006, at 11:52 PM, Norman Palardy wrote:
On Nov 07, 2006, at 9:28 PM, Charles Yeomans wrote:
It seems to me that the following code should generate an error;
that is, db.Error should return true after the second line.
dim db as new REALSQLDatabase
db.SQLExecute "GENERATE ERROR"
This certainly seems like incorrect functionality, but I've been
wrong before.
I'd agree because you've not connected and the SQL is completely
bogus as well
I wasn't perfectly clear; it's the absence of Connect that's the
problem; certainly if I call Connect, then the SQLExecute statement
will result in db.Error returning true.
I understood that quite clearly
You should get some kind of error saying that it's not connected
After that if you are connected you may get a different error for the
SQL
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
