Colin: Thanks for the info...sorry for providing the list with misinformation. :-(
I noticed that UniObjects for .NET is under development and is due for release sometime in mid 2004. Also, the calls to U2 from .NET use SQL not the U2 query language or a READ-type extraction. There's been a lot of traffic here about the difficulties of setting up UniObjects and UniOleDB for use by .NET. I didn't really think it couldn't be done, just not by a challenged individual such as myself. :-) I've seen IBM presentations about their intent to link U2 to .NET and those products are expected to be available in mid to late 2004 (the current set of products were not sufficient). I don't believe that for an MV developer, building an SQL layer to access and update MV data is the optimal MV solution. The PDP.NET product seems to be in the right direction and I assume IBMs forthcoming .NET solution(s) for U2 will be similar. Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [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 > > >-----Original Message----- > >From: Bill H. [mailto:[EMAIL PROTECTED] > >Sent: Friday, May 21, 2004 9:54 AM > >To: [EMAIL PROTECTED] > >Subject: RE: [U2] UniVerse in VB .NET > > > > > >Trevor: > > > >I was under the impression the UniOleDB product was not .NET > >compatible. I > >have been under the impression that the only thing one could > >do to make U2 > >.NET compatible was use either ODBC, fiddle with UniObjects > >for Java, use > >Redback, or use the Pick .NET Data Provider. > > > >Bill ------- u2-users mailing list [EMAIL PROTECTED] http://www.u2ug.org/listinfo/u2-users
