Ray Shahan writes:


Hi all,

I was recently told, by who I consider to be a reliable source, that
IMAGE
no longer uses the extended sort fields to sort a dup entry on a DBPUT.
Try
as I may, I've not been able to substantiate that claim...as far as I
can
tell, IMAGE still uses the extended sort fields (assuming your sort
filed is
not the last field in the set) to sort a dup entry.

http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/mpeix/onlinedoc
s/30
391-90011/30391-90011_top.html&con=/mpeix/onlinedocs/30391-90011/00/00/2
0-co
n.html&toc=/mpeix/onlinedocs/30391-90011/00/00/20-toc.html&searchterms=s
ort&
queryid=20010714-053716

Anyone out there know anymore about this?
----------------------------------------------------
Well, he may be reliable, but he is lacking in Image and/or 3K knowledge.
Image continues and should continue to use extended sort fields.  If it
didn't who know how may applications that depend on this feature would
break.  One thing the 3000 is known is trying very hard to not deliberately
break applications going forward.

However it should be noted that only changing the values of extended sort
fields and only doing a DBUPDATE, will not reorder records on the chain.
You must do a delete/add pair to keep extended sort order on the chain.

Mike Berkowitz
Guess? Inc.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *