> > Some are displayed when called upon with all fields displayed as
> > #deleted, but by adding a filter to that view all data is displayed
> > correct.
> > We have tried to find the solution within the translation of codepages
> > without success. I have no more ideas of what to do.
> > Any pointers or hints would be greatly appreciated.
> I fixed the problem of fields displaying as #DELETED by changing the
> translation setting on the ODBC connection. Have you changed to setting on
> the ODBC connection to allow translation? In Settings>Control
> Panel>Administrative Tools>Data Sources (ODBC), select the ODBC data source
> that you defined, and click <Configure>. Then click the <Translation> tab,
> and click the Radio button labeled "Translate CCSID 65535".
I have tried both ways. In my current setting the button is ticked.
> > In some data can be altered, and in other tables, that operation is
> > not allowed.
> I believe that Access requires a unique key field in order to update the
> file. If the tables that you are attempting to modify on the AS/400 don't
> have a field that is defined as a unique key, it only allows read access to
> the file thru the Access linked table.
In those cases Access normaly allows the user to set the keys when
creating the link. But these tables all got unique keys.
> Steve Landess
> Austin, Texas
> (512) 423-0935
> > We are trying to connect to some tables in iSeries by using Client
> > Access ODBC V5R1M0 on a Windows 2000 client.
> > When trying the connection by using Microsoft Access 2000, it works
> > fine for some tables, but for others it doesn't, in various degrees.
> > /Peter
When trying to import data using the AS/400-data import/export
function provided by Client Access a get this error message:
CWBDB0036 - Servern returnerade ett SQL-fel
SQL0189 - Coded Character Set Identifier 850 not valid.
Cause . . . . . : Coded Character Set Identifier (CCSID) 850 is not
valid for one of the following reasons: -- The CCSID is not EBCDIC. --
The CCSID is not supported by the system. -- The CCSID is not valid
for the data type. -- If the CCSID is specified for graphic or DBCLOB
data, then the CCSID must be a DBCS CCSID. -- If the CCSID is
specified for UCS-2 data, then the CCSID must be a UCS-2 CCSID. -- If
the CCSID is specified for CLOB, DBCLOB or DATALINK data, then the
CCSID must not be 65535. -- If there are multiple DATALINK columns
with FILE LINK CONTROL, they must all have the same CCSID. Recovery .
. . : Ensure that all CCSID values in the statement are supported by
the system and are valid for the data type. For a list of valid CCSID
values, refer to the Work Management Guide.
This error message got me starting thinking the problem was not within
the ODBC-connection itselfe but somewhere in the translation of
codepages. But way then some tables and not all of them?