Angelo Collazo wrote: > After researching the data extraction from an SQL database via > UniData/BCI running on AIX I have realized that a third party ODBC > driver is needed for UNIX to behave like a client. An install > document called "How to set up the Easysoft ODBC-ODBC Bridge with > UniData was sent to me by one of our fellow groupies.( Brian Leach). > I have found the following so far(still searching): > > 1- Easysoft USD 1399.00 for a single license > 2- OpenAccessSoftware USD $995.00 for a single cpu > > Question: > a- Anyone using another lower cost vendor's ODBC driver and can > share the cost? And if so, are you happy with it.
I really don't like the idea of hard-coding SQL for a relational database into code that is in another database. That's really bad form in terms of separation of functions and tiers - anyone who reads material on Design Patterns (Gang of Four, et al) should cringe at this sort of thing. The best approach is to have your U2 code invoke a business process that says "I need data", pass the request up to a tier that specializes in getting that sort of data, and return pure data to your application. If you change which database you're using on the outside (relational, XML or otherwise), or the schema or rules used to interact with your external database, you shouldn't need to change your U2 code. ADO.NET was created to solve problems like this, and mv.NET is an ideal solution for lots of problems that involve exchanging data between MV and other databases and environments. Specifically, you can send your request up from U2 to a middle tier and then use completely free data access tools to get into any one or more databases out there. Write the requests in real SQL, not via BCI, get back a result set, and pass it back to U2 as a set of files and/or dynamic arrays, or callbacks to BASIC programs. Why can't you use UO, UOJ, or UO.NET? These libraries don't provide for server-side triggers that invoke remote events - mv.NET does. There is a license for an mv.NET developer but: 1) You can use mv.NET for _many_ purposes, not just one. It seems like whenever people have a specific problem they get an answer specific to that problem - have another problem, get another answer. With development tools like mv.NET you get one solution to lots of problems, making your collection of tools much smaller and more manageable. 2) End-user sites don't need developer licenses and the low cost for an end-user session license is quite reasonable. This is far better than the above mentioned prices per server - and I believe those products are limited to processing one query at a time, which is hardly acceptable in a multi-user environment. In the next week or so I'll try to write up another freeware offering which will demonstrate what I'm describing above. Your U2 code should just call a BASIC program which makes a request, and the return parameters will be the data you want - with no SQL or ODBC or other stuff involved in the U2 side. My freeware that relies on mv.NET of course requires an mv.NET license - you can contact me for a free evaluation or regular license. Inquiries welcome, especially from someone willing to test the code, or from people with special relational database requirements (SQL Server, Oracle, DB2, MS Access, MySQL, Firebird, etc). Until that's done, some of you may be interested in another freeware offering I wrote that uses mv.NET to invoke any command or query from any MV DBMS from any PC. So you can go to your DOS prompt and run programs in your AIX system, run reports from .BAT files, or shell out from VB code to execute U2 functions and return results for rendering or data transfer, etc. See this link for files related to MVExec: http:// removethisNebula-RnD.com/freeware/ (anti-spam precaution: just copy the text starting at Nebula into your browser address area.) HTH Tony Gravagno, Nebula R&D TG@ again,removethispartNebula-RnD.com ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
