Re: .NET Data Provider translate 65535 -- MIDRANGE-L

Subject: Re: .NET Data Provider translate 65535
From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Date: Mon, 27 Jun 2016 14:40:18 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi Justn

You should probably install the Programmer's Toolkit option of IBM i Access for Windows - there's a .Net Provider Technical Reference there.

The property you want is iDB2Connection.CharBitDataAsString

HTH
Vern

On 6/27/2016 2:24 PM, Justin Taylor wrote:

Does anyone know how to force the .NET Data Provider to translate CCSID 65535? I found an MS doc for OLEDB, and there you used "BinAsChar=true;CCSID=37" in your connection string. Unfortunately, that crashes if you use it with the .NET Data Provider.

Thanks

This mailing list archive is Copyright 1997-2026 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.