Frank Schönheit - Sun Microsystems Germany wrote:
You should be able to do this with other engines, too - aren't you?
No and I never have been able to. I am feeling that we are somehow
talking about two different things.
When executing a statement in the query designer, it is plain sent to
the DB. If the statement does not produce a result set, this is told to
the user, else, the results are displayed. So, UPDATE should work with
any DB, as long as the DB itself supports it.
Where doesn't it work for you?
Everywhere. For example I just opened a HSQL embedded Base file.
Selected 'Create Query in SQL View' task button. In the window I entered
this command
UPDATE "provincies" SET "provincie" = 'xxxxx' WHERE "Id" = 44
[ 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.", now it also does not apply the update to
the table.
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.
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
