.NET Data Provider translate 65535 -- MIDRANGE-L

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

Subject: .NET Data Provider translate 65535
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Mon, 27 Jun 2016 19:24:14 +0000
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>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: .NET Data Provider translate 65535 , Matt Olson
Re: .NET Data Provider translate 65535 , Vernon Hamberg

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.