Are either of the partitions running with QCCSID - 65535? And the ODBC DSNs? There's a tab for translating 65535, I think.

HTH
Vern

-------------- Original message --------------
From: "Rick Carter" <rcarter@xxxxxxxxxxx>



ISeries 550 V5R4

Running LPAE system with two partitions. Partition A is our primary box
and we have several Microsoft Access database jobs that uses LINK
function to ISeries tables and pulls data via ODBC connection down to
Access tables. These all work fine using standard ODBC connection.

Recently, we setup Partition B as a clone of A but are having random
problems with the same type of MS Access tables and trying to LINK to
ISeries tables. In particular we may have one user with 30 different
downloads to Access, and 20 of them might work fine and the other 10 is
giving error message of:

Microsoft Access - ODBC - Call failed
Error 32146 which really doesn't give any information.

When this error occurs, the Access Table is created with the proper
headings form the ISereis file and it even has the right number of
records but all the fields have the #Name? in the fields. This is very
random and we cannot pinpoint why this happens with some of the
downloads but doesn't happen with others.

Both partitions are as same PTF level and both running same versions of
ISeries access or Client Access.
Any suggestions?


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