I wrote previously:
UniBasic does not prevent you from writing out a record or ID with char(0)
imbedded. It is a legal character.
No guesses as to the cause of your particular issue.
To assist in diagnosis, you can search your problem file for all occurances
of char(0) in data records or keys using an option on 'guide'.
For instance:
guide -U0 PROBLEM.FILE.NAME
option is -U followed by the ascii charcter number you want to search for.
I should add that the information about characters found is in
GUIDE_ERRORS.LIS.
For instance:
guide -U65 VOC (looking for 'A')
pg GUIDE_ERRORS.LIS
VOC
File Integrity:
Group 0, block 1, record number 0 = "COL.SPACES"
has char(65) in key.
Group 0, block 1, record number 1 = "LIST.LABEL"
has char(65) in key.
Group 0, block 1, record number 7 = "STATS"
has char(65) in key.
Group 0, block 1, record number 0 = "COL.SPACES"
record has char(65) in data.
Group 0, block 1, record number 1 = "LIST.LABEL"
record has char(65) in data.
... (many more entries)
Wally Terhune
SWG Client Support - Information
Management Software
U2 Support Architect b IBM U2
Client Support Team
4700 S. Syracuse St., Denver, CO
80237
Tel: (303) 773-7969 T/L
656-7969
Mobile: (303) 807-6222
[EMAIL PROTECTED]
Register today for the premier
U2 technical event!
[demime 1.01d removed an attachment of type image/jpeg which had a name of
08633156.jpg]
[demime 1.01d removed an attachment of type image/jpeg which had a name of
08907059.jpg]
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
