Re: Data provider question

I agree. I think I had this in the archives, but I was working on another
non-iSeries project and needed to access the vendor's MS SQL database. LINQ
took about 15 minutes to retrieve 350 records, XSD took minutes, and my own
code took seconds. Very important in any UI application.

--
Mike Wills
http://mikewills.info


On Wed, Jul 14, 2010 at 2:38 PM, Maurice O'Prey <Maurice.Oprey@xxxxxxxxx>wrote:

Manually coding your typed data sets and using the standard IBM data
provider (whichever version 5.3-6.1) is in my opinion the easiest option. I
personally have found that when accessing iDB2 data you cannot expect
VS2010
to generate all the correct code for you due to differences in SQL syntax
etc. (plus your own design wishes)

It's not very difficult and there is no reason to get other ODBC/OLEDB
drivers involved IMHO

Maurice O'Prey


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of
BButterworth@xxxxxxxxxxxxxx
Sent: 14 July 2010 19:38
To: systemidotnet@xxxxxxxxxxxx
Subject: Re: [SystemiDotNet] Data provider question

My goal, in part, is to create a typed dataset, I've determined that in
order to have access to the MS ODBC driver in Data Sources or Database
Explorer, I need the full-blown version of VS Studio, and I'm having
trouble with the IBM 6.1 data provider. I can add it as a reference to my
project, but when I try to add it to the toolbox, I get an error that "the
assembly's manifest definition does not match the assembly reference" even
though the assembly in the GAC is version 12.0.0.0 and the one in the IBM
i Access folder (IBM.Data.DB2.iSeries.dll) is 12.0.0.0. I updated Access
to 6.1 last night, so I'm not sure if there is a problem with my machine
due to a previous version of Access, or if it is something with the new
IBM data provider. I suppose I can manually code my typed datasets.

Blake


------------------------------

message: 2
date: Wed, 14 Jul 2010 08:52:03 -0500
from: Mike <koldark@xxxxxxxxx>
subject: Re: [SystemiDotNet] Data provider question

You can add the IBM driver to your References. From there you can use a
DataSet.xsd object or what I have found is that the connection is faster
when you code your own own connection.

If you want to make use the of the entity framework, I have basic sample
of
setting that up as well.

--
Mike Wills
http://mikewills.info


On Wed, Jul 14, 2010 at 8:43 AM, <BButterworth@xxxxxxxxxxxxxx> wrote:

Hello Everyone:

I am working on a Windows Form application and am using IBM i Access 6.1
and VS Express 2010 to develop it. Is the best data provider to use to
connect to DB2 for IBM i the one provided with Access? I'm asking

because

it would be nice to use a provider that integrates with the Data Sources
or Database Explorer windows in Visual Studio, and I'm not sure that the
Access data provider has this functionality. Is it possible to use an

ODBC

or OleDB provider provided by MS or IBM, which integrates with VS? Right
now, the only eligible providers/data sources are MS SQL Server or

Access,

and it isn't clear to me how to add another provider that could be used

to

access DB2? (Maybe it's not possible in VS 2010, but I haven't had much
luck figuring this out by searching online.) Any advice, links or
direction would be much appreciated.

Thanks,
Blake

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

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