Colin, The only UDT.OPTION that may have changed since the last BUILD.INDEX is number 11, U_DATACOMMAND, to ON. This affects the clearing or not of the data stack when an EXECUTE or CHAIN statement generates a SELECT list and, on the face of it, has no affect on the sort order. A side effect? The formatting of the CONO field is "3R" on the UniData 5.2 system and "3L" on the UniData 6.0.9 system so format justification apparently does not affect this behavior. I also tried changing the index length back to 8 from 50 on the non-production 6.0.9 system with no change.
Karjala >>> [EMAIL PROTECTED] 10/06/2004 1:02:09 PM >>> Did you change any UDT.OPTIONs? I seem to recall that there was one we had to set to get the proper handling of numbers like 001 - although we weren't working with an index at the time. Sorry, I don't recall which option it was.... Hth Colin Alfke -----Original Message----- From: Karjala Koponen [mailto:[EMAIL PROTECTED] ... I recently added an additional alternate index to one of my files. ... The sort order of SELECT JOB WITH CONO = "001" changed from an ascending ID sort before the re-indexing to a descending ID sort after. I did the same things on UniData 5.2 on AIX and UniData 6.0.9 on Solaris 2.8 with the same results. ... ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
