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
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 it
Can someone lay out, in relatively simple terms for a simple guy, when using
UniObjects is the correct approach to developing an application using one of the U2
databases? And, perhaps, when UniObjects would seem attractive but is not, in
reality, a good choice?
And, yes, I am sure that
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 by
