Re: ODBC vs. Objects for OLE

Mark,
I can back up your comments 100%, we are in exactly the same position using OO4O and PL/SQL packages.
We have seen remarkable increases in perfromance plus, as you mentioned, the ability to effectively recode an application without changing the front end. Although we are only working "in house" so to speak, we have a number of sites to look after and this facility is a great advantage.

We have now broken all our apps so that the application itself just takes care of the interface then calls OO4O for database access or Crystal InProc server for reports plus a couple of in-house written InProc servers for security and maintaining local tables. So we basicaly get a sort of 3 tier with COM in the middle teir. Works a charm.

Glad to here someone else is using this combination, feels lonely out here <g>

Rob

Mark Wagoner wrote in message <349e6f3a.832801705_at_news.iac.net>...
>On 19 Dec 1997 21:00:51 GMT, johnj_at_dbbasics.com wrote:
>
>>Does anyone have any experiences between ODBC vs. Objects for OLE.
>>I have been given the task of recommending which is better. I am not
>>a developer, rather I am a DBA so I am not up to date on which is
>>best to use. Please respond if you have any input into the best
>>choice between ODBC vs. Object for OLE. Please mail responses
>>to johnj_at_dbbasics.com because I am off-site for this project so
>>I do not have direct access to the internet. Thanks.
>>
>>John Jones
>>DB Basics, Inc.
>>johnj_at_dbbasics.com
>>
>
>John,
>
>We started developing a rather large system using VB, C++ and Oracle
>on NT a little over a year ago. At that, OO4O was not available (at
>least a stable version) so we used ODBC. We coded to the ODBC API for
>performance reasons but ran into problems using all of Oracle
>features. It also quickly became apparent that setting up a client
>was going to be an administrative problem.
>
>About two months after we started we got a copy of OO4O 2.0 and
>decided to try it with a couple of small test apps. The development
>so so much easier than the API calls and the speed was so much better
>than we quickly stripped all ODBC code and replaced it with OO4O. We
>have been extremly happen with the results. We currently have over
>two dozen customers running the app and I can honestly say that setup
>and administration of the client has not been an issue.
>
>We are now adding enhancements with OO4O 2.2 which will allow us to
>return multiple results sets with a single call to a stored procedure
>(a ref cursor in PL/SQL). We are expecting this to increase
>perofrmance even further and move more of the business logic into the
>database in the form of packages. This in turn will make our remote
>support much easier as we can then RAS into the NT box and load an
>updated version of the package with out changing client code.
>
>In short, if you do not need the capability of connecting to different
>backend databases, ODBC will offer you nothing. In fact, it will
>simply add a layer of fat between your app and SQL*Net. If you are
>going to be Oracle specific, use OO4O.
>
>Mark Wagoner
>Senior Developer
>MedPlus, Inc
>
>To reply, remove no.spam from my e-mail address
Received on Wed Dec 24 1997 - 00:00:00 CST