× 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.



Chris/Melinda - thanks for the tips. The joblog on 400 showed it was looking
for a field name
not in the table (the sql string was truncated at the 255 bytes?). I played
with MS Query
for hours trying to save a "Select * from ..." but every time I did that,
upon re-open, all
the fields were again in the Select statement. I took Melinda's advice and
did MS-Query to Excel, and used Excel as the "get data".
I will need to solve this in the future if you have any ideas how to get MS
Query to behave.
thanks
jim
----- Original Message -----
From: "Chris Devous" <cdevous@xxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, May 23, 2003 1:17 PM
Subject: Re: MS Word/Query AS400 database error


> If any of the data fields are CCSID 65535, you have to explicitly turn on
support in the
> translation tab, but I'd think that would only cause a problem with those
fields and not
> the entire record.
>
> With a 900 byte record, I'd have to say that you shouldn't be running into
any buffer
> size or LOB threshold problems.
>
> Examine the query.  Are you doing a join?  Do you happen to have 2 result
fields with
> the same name?  In Word 97 & 2K, the query string itself can not exceed
255
> characters (even though MSQuery is OK with it).  If you're selecting
columns by
> name, try SELECT *  FROM...
>
> Another thing that can cause this is security.  Check how you connect in
the DSN.
> Do you use the same connection as OpsNav?  Does that profile have rights
to the
> table(s) you are trying to access?  I'd have to say it's likely because
you see results in
> MSQuery, but it is something to check.
>
> If the problem doesn't appear to be query based, see if the 400 side
provider job
> (QZDASOINIT) has any meaningful messages in it's joblog, and turn trace on
in the
> ODBC data source, let the problem happen, and look for anything meaningful
in the
> log.
>
> HTH,
>
> --Chris
>
>
>
> On 23 May 2003 at 11:07, Jim Franz wrote:
>
> > Chris,
> > Both docs use the same data source (i have only one source
> > identified). >From the "working" doc and the "non-working" doc - same
> > source, and files are in same lib. I can preview the data from MS
> > Query, so I know the dsn is working, but when I click Return to MS
> > Word, I get the error. Only difference I can see is the file. As a
> > test I just created a new doc, with new file. No problem. Is there a
> > size limit? The failing doc is getting 30-40 fields instead of 10-15.
> > jim
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> 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-Ups:
Replies:

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.