Nick, We use UV with talking Oracle (using UCI). We're mainly pushing the data from the Oracle end (trigger driven). In another interface to a Oracle-based application, we've got a Tuxedo middleware interface. Yet, again - mainly one-way traffic (from the Oracle end).
I know there is a limitation in UV triggers, that you can't do an SQLConnect, etc (Using the SQL Basic Call Interface -BCI). UD Triggers may have a similar limitation, perhaps not. What platform/OS are you on? Have you looked at UniObjects for Java and the like? Regards, David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nick Southwell Sent: Thursday, February 12, 2004 11:23 PM To: U2 Users Discussion List Subject: RE: UniOLEDB Threading issue Thanks David, I suppose we assumed as many would that an OLEDB driver would handle concurrent requests especially when the documentation talks about UniOLEDB's support for free threading. Frustrating as hell, looks like we will move to a SQL Server caching solution. I have the theory of bidirectional sync in my head, triggers from SQL populating Unidata and I'm thinking about triggers from Unidata populating a control table which SQL polls. Not sure if the Unidata -> SQL can be done in a more efficient manner. Funny enough the first response from IBM was to use their "wonderful" redback product instead. Thanks Nick -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
