I don't have an exact answer, but the developers have
said the .Net provider not working with their
"developing environment". I could get a more exact
answer, but we attempted to do that switch a year
ago and had issues. There are 2 separate win develop
teams with different tools, each for separate app
sets. I'm strictly on the i side.
In prelim testing, our bulk dataload of our nightly
warehouse load will shrink by several hours with
the MS OLE DB (if we can solve this issue).
I do see ptfs related to QRWTSVR but not this issue.
I need something concrete to get ptfs loaded..
Jim Franz
________________________________
From: Maurice O'Prey <Maurice.Oprey@xxxxxxxxx>
To: .net use with the System i <systemidotnet@xxxxxxxxxxxx>
Sent: Mon, November 12, 2012 2:27:39 PM
Subject: Re: [SystemiDotNet] Microsoft OLE DB for DB2 driver issue
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.
midrange.com
