×
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.
Jim
I know this is not what you are asking but why are you using an OleDB driver
and not the native IBM iSeries Access.Net provider? (or whatever it is
called now)?
Granted trimming the blanks may be experienced in both but I'm just curious?
Maurice O'Prey
-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of J Franz
Sent: 12 November 2012 18:13
To: systemidotnet@xxxxxxxxxxxx
Subject: [SystemiDotNet] Microsoft OLE DB for DB2 driver issue
(also posted to midrange-l)
Our network side is testing the DB2OLEDB (SQL Server 2008 R2) in place of
the iSeries Access OLE DB driver and one big issue...
The sql request is handled by QRWTSVR where the iSeries Access went through
QZDASOINIT.
In the result sets, all the character fields have the trailing blanks (fixed
length, not trimmed) where as the iSeries Access OLE DB result sets were
trimmed.
Any idea how this is controlled? Too many apps to modify.
V6R1 w/cume 1256
Jim Franz
--
This is the .net use with the System i (SystemiDotNet) mailing list To post
a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.
As an Amazon Associate we earn from qualifying purchases.