Kathy Vance wrote: > ... We have the > problem to make SQL 2000 communicate with Universe 10 or > 11 with IBM Universe ODBC driver. Based on its document, > this driver seems do not support the SQL server. > > Could you share your experience on the way of using > OpenLink ODBC driver for SQL server?
Kathy and others : this thread relates to more direct comms between U2 and a relational database, sometimes U2-initiated. Another way to exchange data between environments is to use a middle tier: U2 <--> middleware <--> relational This is one of the many reasons for the existence of ADO.NET, to serve as a sort of universal, DBMS-independent hub between databases. It's very easy to get your U2 data into an ADO.NET dataset, and anyone who understands SQL can move data to/from that dataset and a relational database. So the answer may not be to tie your U2 environment directly to relational but to have a middle-tier push/pull data from both sides as needed. Triggers can be developed so that transfers can be initiated from either side. If one system or the other is down you don't need to hold up the other end of the process, you can store data in the middle-tier until the other server is up - this may or may not be desirable depending on the app. Using a middle-tier also keeps platform-specific code out of your application - that is, you don't hardcode Oracle SQL into your U2 app which may need to be modified for SQL Server, MySQL, DB2, MS Access, etc., and your relational DBA people don't need to understand U2-specific nuances either. You also don't have to worry about some relational database supporting your U2 drivers, or vice versa. We're very pleased with mv.NET as a tool that facilitates communications with many MV DBMS platforms. In particular, mv.NET has a great ADO.NET interface specifically designed for doing what people in this forum say they want to do with U2. That is in addition to or instead of coding with syntax that closely resembles MV BASIC syntax. Sure, you can use UO or UO.NET but you still need to code the ADO.NET interfaces yourself, this is all included in the standard mv.NET product in addition to many other valuable and unique features. As a Distributor for mv.NET I'll be happy to discuss requirements and propose a solution to suit your needs. If mv.NET doesn't fit, I'll say so immediately. If you're not familiar with .NET development and want to do development yourself, we can provide all levels of education from beginning to expert through our partners who specialize in .NET training. We also offer development services to write your code to-spec and provide all required support. One of the major reasons why we decided to sign up with BlueFinity International to resell mv.NET is their absolute dedication to the product. Their support is phenomenal. They fix issues and enhance the product, sometimes faster than we can keep up with them. Their documentation is excellent and continues to evolve to meet developer needs. I've reported a number of anomalies in product and docs that were addressed and available in a new cut the next day. Our goal is to find VARs who want to enhance their apps with mv.NET, and by offering similar high quality support to our partners, we're building a very happy channel of developers and end-users. Please feel free to contact me for more info - it can't hurt to chat. Thanks for your time. Tony Gravagno Nebula Research and Development TG@ removethisNebula-RnD.com ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
