Savita, Whoa, just a minute, nobody said anything about selecting @ID.
Since the @ID (standard alias for the key attribute(s)) is guaranteed to be distinct, including it as a column in your query results means that the rows in your query results are guaranteed to be distinct, whether or not you specify "UNIQUE" or "DISTINCT" in your (RetrieVe or SQL, respectively) SELECT statement. All of the examples given were selecting parts of the @RECORD, (standard alias for the non-key attribute(s)), not selecting @ID. If you want to select distinct non-key attributes, and then select a single random @ID key for each distinct row, the easiest method is to write an ascii sequential file, and then use the Unix/Linux "sort -u" command with your UniVerse non-key attributes specified as the Unix/Linux sort-keys [e.g. "-k 2,9999" if @ID is in column 1.] and then "cut -f1" to get the @IDs. You could also get a single random @ID for each distinct values of some row of non-key attributes via a UniVerse xref file (or INDEX file), provided that the combined length of your non-key attributes (or @AK) is always less than 255 chars. > -----Original Message----- > From: Savita > > Can this (selecting only those order IDs which > have unique combination of Mfg.No and Part.No) *** The information contained in this e-mail message may be privileged and confidential information and is intended only for the use of the individual and/or entity identified in the alias address of this message. If the reader of this message is not the intended recipient, or an employee or agent responsible to deliver it to the intended recipient, you are hereby requested not to distribute or copy this communication. If you have received this communication in error, please notify us immediately by telephone or return e-mail and delete the original message from your system. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
