RE: When is developing with UniObjects the correct approach?

2004-03-01 Thread Karjala Koponen
Brian and Jason(?), Thanks! Karjala >>> [EMAIL PROTECTED] 03/01/2004 4:46:26 AM >>> ... UniObjects is the quickest route for client/server work with U2. It emulates the native model for direct file and stored procedure operations - you open a file, read a record by key, perform operations, write

RE: When is developing with UniObjects the correct approach?

2004-03-01 Thread Brian Leach
Karjala, UniObjects is the quickest route for client/server work with U2. It emulates the native model for direct file and stored procedure operations - you open a file, read a record by key, perform operations, write it back. Fast and very efficient for transactional applications. The advantage/

RE: When is developing with UniObjects the correct approach?

2004-02-27 Thread Marc Harbeson
Can you show us an example of how you are wrapping the UniObject in a COM object? I've never done it this way and am curious how to do it. I have used the UniObjects in ASP.NET with no issues. Works nicely with a U2 backend process pumping out XML. >because of threading issues, but I've success

RE: When is developing with UniObjects the correct approach?

2004-02-27 Thread jasonp
>From my experience, I really haven't encountered a situation where I'd recomment not >using UniObjects when accessing a U2 database from an outside application. I've >heard people say you shouldn't use it directly from ASP because of threading issues, >but I've successfully gotten around that