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] Sent: Wednesday, October 06, 2004 7:45 AM To: [EMAIL PROTECTED] Subject: [U2] UniData index sort oddness I recently added an additional alternate index to one of my files. Procedure: DELETE.INDEX JOB ALL CREATE.INDEX JOB CONO <fourteen other fields> DESC at the prompt for length I entered 50. BUILD.INDEX ALL I changed the length from 8 to 50. 8 was already too short for some of the existing indices and DESC, the newly added alternate index, can be rather long. 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. The dictionary item CONO was unchanged during this process. I don't believe we have any process that counts on the sort order but still, any ideas what's happening? Karjala ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
