@FDibbins - Alrighty! I realize now that I was unclear about what the scenario is. Consider the following: binsort1_unique.xls
I have a bunch of objects in a list. Each object has a unique number (column A), and each object is contained in a bin (column B); as you can see, each bin can hold multiple objects. Each object has several defining characteristics, and in this example I have chosen color and shape (columns C and D).
When all objects are entered in, I want to be able to sort them in various ways. I want to keep the bins in order so that the first objects in the list are still in bin 1, the next objects are still in bin 2, etc. so I first sort by bin and then by whatever else I want. That's all well and good for when every object is unique, as in the above example. However, this changes when I have duplicate items.
Here is another example: binsort1_nonunique.xls
It is similar to the previous example, except now I have duplicate items (objects 1, 3, 5, and 9 are blue circles, for example). When I go to sort, I still want the bins to stay in order, however I need duplicate items to be placed among the bin group containing the earliest instance of that item. For the objects above, it would look something like this: binsort1_nonunique_sorted.xls
I still need the freedom to be able to sort the objects in each bin based on whatever characteristic I want, so having a "bin new" column seems like the best way to help with that. Unique items would keep their old bin number, and duplicate items would be assigned the lowest old bin number of all the items in the matching item set.
So for the unsorted list (the second file in this post), the addition of the "bin new" (column F) would look like this: binsort2_nonunique.xls
And the sorted list (third file here) would look like this: binsort2_nonunique_sorted.xls
Continued on next post due to attachment limit.
Bookmarks