When using ODBC to access the database you can force data to be transalted
when coded with CCSID 65535 by placing "TRANSLATE=1" in the connection
string (for DSN-less connections) or by checking "Translate CCSID 65535"
under the "Translation" tab when configuring a DSN.
When using OLE DB and IBM's IBMDA400 provider (which is faster btw), you
cannot put the translation in the DSN.
Does anyone know how to force a translation from CCSID 65535. Any help
would be fantastic.
Darren Bell
Senior Software Developer
Dolby Laboratories Inc.
email: mailto:d...@dolby.co.uk
Why not approach this instead, from the perspective that the column
definition is wrong; that the idea for correcting the problem could be to
tell the software the column's data should actually be translated. That
is, give the field a CCSID.
Regards, Chuck
All comments provided "as is" with no warranties of any kind whatsoever.
A temporary circumvention would be to use the Client Access Express String
converter object (part of the Express data manipulation objects) to do the
conversion. There is an example in the toolkit.
--
Other Client Access OLE DB resources:
Home page: http://www.as400.ibm.com/clientaccess/oledb
AS/400 Worldwide Technical Support Line Knowledge Base (the "Client Access
OLE DB" section).:
http://as400service.ibm.com/s_dir/slkbase.nsf/112b7bbd01d60eb4862565d8007680
1a?openview&start=1&count=30&expand=3.4#3.4
Toolkit email address: too...@us.ibm.com.
Darren Bell <dj...@dolby.co.uk> wrote in message
news:37cf8...@nnrp1.news.uk.psi.net...
> We are using Internet Information Server 4.0 running under NT Server 4.0
> (SP5). To gain AS/400 access from ASP pages we use Client Access Express
> V4R4 PTF level SF57098. OS/400 is at V4R3.
>
> When using ODBC to access the database you can force data to be transalted
> when coded with CCSID 65535 by placing "TRANSLATE=1" in the connection
> string (for DSN-less connections) or by checking "Translate CCSID 65535"
> under the "Translation" tab when configuring a DSN.
>
> When using OLE DB and IBM's IBMDA400 provider (which is faster btw), you
> cannot put the translation in the DSN.
>
> Does anyone know how to force a translation from CCSID 65535. Any help
> would be fantastic.
>
I forgot to mention that the files are Mapics files. Our files are all
CCSID 37 and work fine.
Thanks for response though.
In the meantime I had a response from IBM that the IBMDA400 OLE DB provider
that comes with Client Access Express V4R4 does not support translation of
CCSID 65535.
In the next release of CA the provider WILL support this function.
I guess we'll have to wait for that one.
--
Darren Bell
Senior Software Developer
Dolby Laboratories Inc.
mailto:d...@dolby.co.uk
Charles R. Pence <crp...@vnet.ibm.com> wrote in message
news:37CFD808...@vnet.ibm.com...
> Darren Bell wrote:
> > We are using Internet Information Server 4.0 running under NT Server 4.0
> > (SP5). To gain AS/400 access from ASP pages we use Client Access
Express
> > V4R4 PTF level SF57098. OS/400 is at V4R3.
> >
> > When using ODBC to access the database you can force data to be
transalted
> > when coded with CCSID 65535 by placing "TRANSLATE=1" in the connection
> > string (for DSN-less connections) or by checking "Translate CCSID 65535"
> > under the "Translation" tab when configuring a DSN.
> >
> > When using OLE DB and IBM's IBMDA400 provider (which is faster btw), you
> > cannot put the translation in the DSN.
> >
> > Does anyone know how to force a translation from CCSID 65535. Any help
> > would be fantastic.
>