On Nov 08, 2006 5:25 AM, Norman Palardy wrote: > 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. > >> [snip] > 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
I also agree this is incorrect functionality and it should generate an error if not connected. But I suspect RS would evaluate a bug report for this as "Not a bug" because you didn't connect to the db - the LR says for the Database.Connect: "Before proceeding with database operations, test to be sure that Connect returns True". So, file a feature request instead. In a big project that intensively uses db operations it's easy to forget to do this check and then it's very difficult to find where the problem is if the db does not give any error when not connected. I hope Marco or Will read this to give us their opinion in order to file a bug report or a feature request. I would like to see this fixed or implemented. Carlos _______________________________________________ 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>
