|
I wouldn't worry about the statement that the functions are not tested, that's simply CYA-wording for "we didn't deal with that in this redbook." Remember, the redbook addresses a specific function, it isn't general documentation. As for there being no advantage using OLEDB in .NET, on one level I agree. You're leaving managed code to drop down to an older technology like COM. From the DB access point of view it's no better than using VB6. However, there's a lot to your application other than the wrapper around the database, and .NET gives you great advantages everywhere else. Finally, I was never a big fan of COM objects for accessing the iSeries as anything other than a database anyway. Make life easy on your application developers and isolate all the iSeries-unique stuff (msgq, dtaq, rla, etc.) on the server side using stored procs. The client is optimized for SQL, deal with it, use it, and make the best of it. -Walden
As an Amazon Associate we earn from qualifying purchases.
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.