Basically the dict items were never defined.
create an I-type
REC.LNG
001 I 002 COUNT(@RECORD,@AM) + (@RECORD NE "") etc
THEN
SORT file BY-DSND REC.LNG REC.LNG to see the records with the maximum number of attributes.
this isnt 100% full proof since there may be some program out there that does write beyond the max # of attributes, however the logic in the program hasnt been triggered yet
Rich
Brutzman, Bill wrote:
At the bottom of a data dictionary having a few dozen D-Fields, I added a few more D-Fields.
Inside a UniBasic application, end-users are able to read and write data to these fields.
Sometimes though, when listing results, some flaky data shows up.
I am writing to inquire...is there now a requirement to "normalize" all records such that there are "blanks" specified in the newly defined fields...for all records ?
In other words, is it not ok to have a mix of records...some with 71 fields...others with 75 fields?
--Bill -------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
-- Richard A. Wilson Lakeside Systems Smithfield, RI, USA ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
