|
Dare, Sorry about the earlier fat-finger. Records #1 & #9 look appropriate, the attribute field is populated by either characters or blanks. #20 and #329 have some obvious garbage; the characters are not padded with blanks but with some non-displayable characters. Now how did that get there? Andy Nolen-Parkhouse > Hi guys, > > This morning, I went through the file field by field trying to recreate > the > error and I found the culprit FIELD. It is the attribute field, when I > eliminate this field the file works fine and when I select the field when > it > is blank. Now, I went to DBU and display the HEX values in this field for > all 512 records. These are my values: Most of the records are like > record > #1. > > Record# Object Object type Object attribute > > 1 ACCGSODTA *USRPRF 0 > CCCCEDCEC4 5EEDDDC4 4444444444 F > 1337264310 C4297960 0000000000 0 > > 9 AKERS_MA *USRPRF QSECOFR 0 > CDCDE6D444 5EEDDDC4 DECCDCD444 F > 12592D4000 C4297960 8253669000 0 > >20 AM2000 *USRPRF QSECQSPO 0 > CDFFFF4444 5EEDDDC4 DECC00DEDD F > 1420000000 C4297960 8253218276 0 > >329 QDBSHR *USRPRF *IBMQRJE 0 > DCCECD4444 5EEDDDC4 5CCD00DDDC F > 8422890000 C4297960 C924818915 0
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.