We can confirm Colin's statement. We are currently developing a new web application using ASP.NET and C#. We are accessing UniOLEDB (with UniData 6.0.12) through the COM interop capabilities of .NET from C#. We had some minor problems with the connection, but our developers eventually got something working. I'll see if they can provide some input. Right now they are chained to their workstations, trying to make up a missed deadline. <grin> The only other problem we had were some random E_FAIL and SQL Rowcount errors. IBM supplied a patch that dealt with some threading issues, which fixed the problem. The only bridge we have not crossed yet is having multiple window services running our C# code, each having an OLEDB connection open. The window services will get their transactions through a set of MSMQ queues.
Glenn Batson JIA, Inc. (www.jenkon.com) Vancouver, Washington -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, May 21, 2004 9:11 AM To: [EMAIL PROTECTED] Subject: RE: [U2] UniVerse in VB .NET Not true. See www.ibm.com/software/u2 there is a link to a White paper: Using IBM U2 and Microsoft .NET. or for those too lazy to look through the page: ftp://ftp.software.ibm.com/software/data/u2/pubs/whitepapers/ibmu2-microsoft net.pdf hth -- Colin Alfke Calgary, Alberta Canada "Just because something isn't broken doesn't mean that you can't fix it" Stu Pickles ------- u2-users mailing list [EMAIL PROTECTED] http://www.u2ug.org/listinfo/u2-users
