Corrected....
Barbara Duprey wrote:
John Toliver wrote:
See below:
On Sun, Dec 21, 2008 at 20:46, Barbara Duprey <[email protected]> wrote:
I think you need something like this in the SQL command window:
UPDATE 'your_table' SET 'your_field' = RTRIM('your_field')
JT- I created my string in two ways:
1: "UPDATE TestMedData SET TestMedData = RTRIM(Major/Common Side
Effects)"
<without the quotes at the ends of the string> and received this
response:
"4: Table not found in statement [UPDATE TestMedData]"
You UPDATE the table and SET the field -- so the first reference is to
the table name, and the other two are both to the field name (the
RTRIM function returns a string from a string that is provided either
as a literal or by reference). The quotes are not necessary for
TestMedData, but they would be for Major/Common Side Effects, with its
embedded spaces and punctuation. Ariel says these need to be double
quotes to identify a reference, rather than single, so I guess the
source I used had it reversed; I haven't done this in a while. But if
you clear up the table name and field name references, you should get
what you want, I think.
OK, I tried this on a test database in 2.4.1 on VistaHP. The
double-quotes are needed for all references. I created an mbedded HSQLdb
database named Test, with a table TestTable consisting of an
auto-increment ID primary key field and a VARCHAR field named
TestString. This command, entered in the window provided via Tools >
SQL, worked to remove all trailing blanks from the TestString field:
UPDATE "TestTable" SET "TestString" = RTRIM("TestString")
2."UPDATE 'TestMedData' SET 'TestMedData' = RTRIM('Major/Common Side
Effects')" and received this response: "5: Unexpected token:
TestMedData in
statement [UPDATE 'TestMedData']"
Now this feels like I simply am missing the proper syntax for issuing
this
SQL command, but I created the test table and pasted the name from
the table
into the template you wrote for the SQL string the difference
between the
two was the quotes surrounding the name of the table "TestMedData".
thanks for your help, I do appreciate it.
John T.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
