Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!agate!linus!progress!mikep From: mikep@progress.COM (Mike Pacholec) Newsgroups: comp.databases Subject: Re: Progress help needed Keywords: Progress, Primary Index, Change Message-ID: <1990Oct30.220640.13606@progress.com> Date: 30 Oct 90 22:06:40 GMT References: <2268@bnlux0.bnl.gov> <2280@sparko.gwu.edu> Sender: news@progress.com (The News User) Organization: Progress Software Corp., Bedford, MA Lines: 36 Nntp-Posting-Host: mikep fc185120@seas.gwu.edu (Lish Ethan A.) writes: >In article <2268@bnlux0.bnl.gov>, lally@bnlux0.bnl.gov (keith lally) writes: >> >> Help! After creating a primary index for a file, I now need to change >> it to sort ascending. How can I do this in PROGRESS(tm) 5.2I? >> >> thanks! >Hello - >This may be accomplished by defining an secondary index with the attribute >of ascending. Then when you desire that the data be accessed in that manner, >you would include the "USE-INDEX " in the "record-phrase". > I hope this helps, > Ethan A cleaner solution is simply to delete the incorrect index and create a new index on the same field. Because the incorrect index is the primary index in this case, temporarily select a new primary index before trying the delete. If the incorrect index is the only index on the file, then create a dummy index to be the primary, and delete this index before committing your changes. There is no need to treat the incorrect index as a permanant gaffe. ------------------------------------------------------------------------------ Mike Pacholec UUCP: mit-eddie!progress!mikep Progress Software Corp. Internet: mikep@progress.com Bedford, MA -- -------------------------------------------------------------------------------- Mike Pacholec UUCP: mit-eddie!progress!mikep Progress Software Corp. Internet: mikep@progress.com Bedford, MA