× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I’m getting this error when using the Excel upload facility to transfer a
simple (3 columns, 600 rows) Excel 2000 spreadsheet from my Win2K desktop to
a V5R1 system:

CWBDB0036 - Server returned SQL error

SQL0104 - Token ) was not valid. Valid tokens: CHAR LONG BINARY DOUBLE
GRAPHIC CHARACTER <IDENTIFIER>.

Cause . . . . . :   A syntax error was detected at token ).  Token ) is not
a valid token.  A partial list of valid tokens is CHAR LONG BINARY DOUBLE
GRAPHIC CHARACTER <IDENTIFIER>.  This list assumes that the statement is
correct up to the token.  The error may be earlier in the statement, but the
syntax of the statement appears to be valid up to this point. Recovery  . .
. :   Do one or more of the following and try the request again: -- Verify
the SQL statement in the area of the token ). Correct the statement.  The
error could be a missing comma or quotation mark, it could be a misspelled
word, or it could be related to the order of clauses. -- If the error token
is <END-OF-STATEMENT>, correct the SQL statement because it does not end
with a valid clause.


The wizard appears to make it simple, I’ve done this in the past, and I can
do it with Client Access Express.  I’m current on service packs all around.

Suggestions will be appreciated!

Thanks,
Reeve
--




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.