×
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.
Our developer through trial and error (and me helping out some)
discovered
that OLE DB for queries and ADO.NET for inserts/updates/deletes worked
best.
I haven't worked through his code to see how he had set it up yet, but
it
seems to be working for him.
If it from .NET he's using ADO.Net for all data access. I think you mean
OLE/DB for queries and the managed provider for updates. ADO.Net sits on
top of both.
While you may have found that that mix is "best" I would question that
for several reasons, none of which have anything to do with which is
faster. By splitting your data access between two methods you've
effectively doubled the number of connections needed to the System i for
your application. Also, you've made your programming more complicated.
You now have to think about which type of access you're doing and use
the correct connection/connection-string. This makes it that much harder
to encapsulate your data access, and removes any possibility of a nice
simple GetConnection() method.
Unless you're seeing _major_ performance differences between the
managed-provider and ole/db I'd stick with one. And major is perhaps an
order of magnitude better, and I'll be impressed if you're seeing that.
-Walden
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
midrange.com
