× 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 multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Did you look at here
http://faq.midrange.com/data/cache/194.html

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Vernon Hamberg <vhamberg@attbi.com>
Sent by: midrange-l-admin@midrange.com
04/30/2002 06:55 PM
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Fax to:
        Subject:        Re: Excel spreadsheet upload problem


You say you can do this in CAE. What, then, is the Excel upload
facility? Is that something in Excel, not in CAE? I tried the CAE
'Transfer Data to AS/400' in Excel 2000 in Win98SE. It's an add-in
from when I installed CAE.

On Mon, 29 Apr 2002 10:18:19 -0400, "Reeve Fritchman"
<reeve@ltl400.com> wrote:

>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



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.