Hi Andrew, > [ I know this is valid as I can apply it in the SQL window ] attempting > to execute the query at this moment generates the error box with this > message - "The given command is not a SELECT statement. Only queries are > allowed." > > Turning SQL direct on and trying to execute the query generates this > error message - "The data content could not be loaded. Statement does > not generate a result set.",
'til here it's as expected. Probably not as it could be, ideally, but as expected. > now it also does not apply the update to the table. Hmm, you caught me, this in fact does not work. Seems that some (probably all except the sloppy ones :) databases reject non-SELECT statements in the API call we use (which is intended for SELECT statements). Okay, I withdraw what I said. > I did the above with version 2.0.3. > Using dev build 178 it is slightly different. Under this build I cannot > even save the query - an attempt to save generates the error box telling > me only SELECT queries are allowed. Which probably is also issu 67453, fixed in m181. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
