×
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.
I am certainly no expert on SQL Server (or IBM i and midrange system for that matter, even after 40 years - and I have been using SQL since 1985...)
As I continue down the SQL Server rabbit hole, I have run into some other challenges as well.
It appears that when using the IBMDASQL OLE DB driver that the tables on the IBM i system are read-only unless they are either journaled or located in a collection (which by default, are journaled).
I have not found any setting available in Provider String which allows you to specify the commit level for the IBMDASQL driver.
ODBC Advanced server options allow you to specify Commit Immediate (*NONE), which allows write/update/delete on IBM i tables. Although not recommended for production purposes, I have on several occasions used VBA with an ODBC connection to read/write/update/delete IBM i tables (in most cases my alternative to using File Transfer or CPYFRMIMPF when dealing with trashy PC data.)
I'm looking for recommendations and pros/cons on the database Providers to use with SQL Server - should I instead use the Microsoft OLE DB Provider for DB2 ?
Regards and TIA,
Steve Landess
(512) 289-0387
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
