This is exactly the methodology I use and we've yet to have a problem...Call to COM object, object opens connection, gets data, closes connection. I wouldn't recommend this methodology in an environment where you were dealing with a large number of simultaneous users or transactions, but we've load tested it up to 50 simultaneous users on a Windows 2000 server running IIS (Dual P-4 2GHz, 1.5 GB Memory) along with 100 other users pulling static html without significantly degrading resources and no problems on the UniObjects side of things.
-----Original Message----- From: Martin Scholl [mailto:[EMAIL PROTECTED] Sent: Monday, June 28, 2004 11:45 AM To: [EMAIL PROTECTED] Subject: RE: [U2] UniObject Problem UniObjects is not thread safe (Will be hopefully with the .NET version that comes out any day now). The connections cross. With every database interaction from ASP, I open the connection, do my read, write etc and disconnect. I don't know if this is really safe so I am awaiting UniObjects.NET impatiently. Martin Scholl President HIPAAsuite 18910 New Hampshire Ave Brinklow, MD 20862 301-924-5537 Phone 301-570-0139 Fax 301-613-9572 Cell ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
