It was a permission issue -- I blame Friday. Thanks.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Colin Alfke Sent: Friday, November 04, 2011 2:31 PM To: 'U2 Users List' Subject: Re: [U2] OPENSEQ / WRITESEQ and UniObjects I'd guess it was some type of permission error. Does the user you are connecting with through UniObjects have write permissions on the folder that the open/writeseq is writing on? hth Colin Alfke Calgary, Canada -----Original Message----- From: Holt, Jake It fails to write. It gives the failure to open error as well, but I believe that is fairly standard if the file doesn't exist before hand. It operations normally, just doesn't write the records to the file. -----Original Message----- From: Steve Romanow I don't know if we have enough information. Does it start? No output whatsoever? IIRC, you can tell writeseq not to cache and to write to disk immediately. On Fri, Nov 4, 2011 at 3:03 PM, Holt, Jake wrote: > I wrote a program to export some data using openseq/writeseq (to a > local server drive, tried a UNC path too) and it works perfectly until > I try to call it using UniObjects. Is this normal behavior? If so, > anyway to make it work with UniObjects? _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
