Subject unconventional index From Charlie <tm@tc.com> Date Tue, 12 Dec 2023 10:20:24 -0500 Newsgroups dbase.getting-started Wow..  I think I just came up with an easy solution since I am not showing the sku anyway.  I'll use A instead of P in the sku.  Make sense? Charlie Wrote: > Thanks so much for the info!   > > OK the order I would like comes after the 4 digit date.  Every numismatic book or reference that I have ever seen shows the date then the initial for the mint it was produced in.  Most US coins do not show the 'P' for the Philadelphia mint probably because that is where the majority of US coins were produced.   And thus The coin books, etc. always show the Philadelphia minted coins first for each date.  Like this: > > 1878 P > 1878 CC > 1878 O > 1878 S > > I am trying to go in this order, however if this becomes too much of a pita, I've been known to go against the grain and it won't be a huge deal. > > Mervyn on another note I have decided to go without the autoincrement order which I realized yesterday will cause more problems when adding new data.  We talked about this a while ago.  I have made all sku field entries unique for indexing and bookmarks..   > > Mervyn Bick Wrote: > > > On 2023/12/12 00:03, Charlie wrote: > > > I don't know if this is possible but is it possible to alter an alphabetical order using an index of some kind?? > > > > > > Example being instead of having a table indexed alphabetically, like ABCDEF.  Somehow alter the order like ACBDFE? > > > > > > Thanks for any comments. > > > > > > > > > > The only way you're going to be able to do this with a .dbf table is to > > add a field to your table as Tim has suggested. > > > > If you can't develop an algorithm that will create the sort order you > > need I'm afraid you will need to populate the sort field by hand which > > could be a real PITA. > > > > If you give us an idea of just how you need to rearrange the list > > someone may come up with some code. > > > > Mervyn. > > > > > > > > >