Martin How are you parsing this information? If you are using the Command.exec to do this then check that you are handling buffering using the command.status, command.next, etc.
The other trap is make sure that the indices you are using to access the dynamic array are not integers where you are trying to extract from a position that is beyond the limits of an integer. I have used very large dynamic arrays and have had no corruptions. Regards David Jordan U2UG Founding Director -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Scholl Sent: Monday, 24 January 2005 1:31 PM To: [email protected] Subject: [U2] UniObjects and VB.Net I am using UniObjects ( the pre .Net version) in a VB.Net ASP.Net application. I am populating a UniDynArray with a file parser. The Array is large, more then 300 attributes. When I run this parser, my array is mangled. Attribute contents are mixed with each other, attribute counts don't match with what I wrote in the code. When I run the code in the debugger, nice and slowly, I don't see a problem, only that sometimes it takes a second or to, for the UniDynArray to come back from a call. But when I run full speed, the mangling happens. It looks like VB.NET starts several threads to deal with UniObjects, does not wait until the thread is finished and then mangles the different pieces. Sometimes I get System.Runtime.InterOp.COMExceptions. Has anybody had similar problems? Found Work-arounds? I can't move over to Uodotnet yet. THere is too much code. I though of parsing my file into a Uodotnet.UniDynArray but then I saw that I can't even initialize a .Net UniDynArray with a session object. 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/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
