In response to Charles Stevenson, who said: IIRC, UD routinely (usually? often? always?) stores data more like UV's "large records". ---------------------------------------------------------------------------- ----- Unidata stores a key/displacement table at the beginning of each group, and does not store the key physically with the data in the record for any record (other than the first record in the group, since the key list begins at the back end of the table and is stored in reverse order). UniVerse's large record handling, if I read the documentation correctly, stores the ID in the main body of the group at the position where the record would normally be stored, but places the data in an overflow area. The differences between the two U2 products are interesting if you are into optimizing file-sizing, or if you find a particular technique in your programming tends to work better or worse on one than on the other, as this thread seems to have demonstrated. I suspect the 'better' and the 'worse' are evenly distributed, though, so please, no 'flavor' (or 'flavour', depending on your location when you learned to spell) wars! ;-)
Susan M. Lynch F.W. Davison & Company, Inc. CONFIDENTIALITY NOTICE: This e-mail message, and any accompanying documents, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution or copying is prohibited. If you are not the intended recipient, please contact our office by email or by telephone at (508) 747-7261 and immediately destroy all copies of the original message. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
