That looks like SQL to me, so I don't see what he means by 'native'. That
same code will work against the System i, provided he sets his connection
string to use one of 6 possible .NET data providers. One of those is the
ODBC provider, which is exactly what he's using in the example you've
provided.
There seems to be a disconnect between your VB guy and the world... he needs
education in both .NET and System i realm.
BTW, I just wrote an article on data providers in .NET:
http://www.centerfieldtechnology.com/publications/
Also, Richard Shoen has written about .NET integration before as well as
Michael Sansoterra and Craig Pelkie (just to name a few off the top of my
head).
There is a good redbook on the topic as well.
HTH, Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: Re: VB Native Data Access on i-series database
Below is what I found (Again, I'm not familiar with VB at all):
Statement below uses ODBC:
Dim cmdMcbellRead As New OdbcCommand("SELECT REFKEY,
SUBSTRING(REFDAT,1,30) FROM " & libBOSS & ".REFERPL10 WHERE REFCAT='CUC'
AND SUBSTRING(REFDAT,31,3)='NAT'", cnMcBell1)
Statement below uses native access (which he said is not support for
iseries database):
Dim cmdSalesDelete As New SqlCommand("Delete From dbo.NAMGroups",
cnSales)
"Grizzly Malchow" <grizzlym@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:<mailman.7526.1228406010.13295.midrange-l@xxxxxxxxxxxx>...
I'm not sure what Native Database Access for VB is, but I know OLEDB and
ADO can be used in VB to access the DB2 database on the System i. If I
remember correctly Client Access has data providers for ODBC, OLEDB, and
ADO. All of which can be used in VB provided that Client Access is
installed.
