It sounds like a program bug. Is the VB client, properly handling record locks. It sounds like the old trap in Basic where if one does a readu and only uses the else option, then the lock forces the else option where the assumption is a new record.
David Jordan Managing Consultant [EMAIL PROTECTED] Mobile: 0428 669 730 DACONO Holdings Pty Ltd www.dacono.com.au PO Box 909 Lane Cove NSW 2066 Australia Phn: 61 2 9418 8320 Fax: 61 2 9427 2371 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, 23 December 2005 6:39 AM To: [email protected] Subject: RE: [U2] UniObjects intermittent problem We are using VB.Net with Redback and there was an issue with the ampersand character ('&') and no data would be transmitted to the backend after the & character. > -----Original Message----- > From: Brenda Price [SMTP:[EMAIL PROTECTED] > Sent: Thursday, December 22, 2005 9:54 AM > To: U2-Users (E-mail) > Cc: Tim Williams > Subject: [U2] UniObjects intermittent problem > > We have a process that 99.9% of the times works great. Considering, I > have 57 > missed up records in the last 4 months and we do an average of 2000 per > day. > We use both VB6 and VB.NET and it happens for both. > > Sometimes the writefield wipes out all the fields upto the field it > updated. > This makes me think for some reason when it goes to do the write.field it > does > not see the record and thinks it is writing a new record. > > There is 3 different scenarios this happens. > > 1. PC process connects to the Universe, selected the data, processes each > record, passes the data from each record to WORD for a word merge, prints > the > resulting document, then updates via the writefield the date flag showing > the > record was printed. In this instance it is field 4, when it happens here, > the > record is thus > > <1> > <2> > <3> > <4> 13854 > > This process connects every some often (5 minutes at the moment - we can > change the timing) and does this through out the day. Plus we run this > process in a batch mode in the evening, this picks up any record we set to > be > in the batch process, select ranges from 700-3500 records. > > 2. Add another twist to this. We also have a VB product that connects to > Universe, passes in data, a UV subroutine creates the record in batch mode > so > it is not picked up immediately by the above process. Once the record is > created, the VB process attaches files to it, then does a write.field to > change the mode from batch to immediate. (simple Y/N field). It will > also > blank out everything but the 2 fields it was trying to update. > > 3. Add a 3rd twist, it makes it through 1 or both processes listed above > and > the document is being faxed instead of printed. We write back a field > showing > it went "Y" or it failed "F" . When it does this, the record is blank > except > for the "Y" or "F" in field 26. > > Any ideas I can pass to our VB folks? > > Thanks, > > Brenda Price > > > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.371 / Virus Database: 267.14.3/209 - Release Date: 12/21/2005 > ------- > 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/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
