No, the kind of sorting (more like ordering) I was looking for is more defined by an assessment of the content. For example, lets say you build a list of the steps you need to paint your house...
consultant on color options
define quantities of paint needed
decide if price is a significant factor
seek qualified estimates
purchase paint
are more painters needed or is this diy?
schedule a sequence of rooms to be painted
etc
Now, it might be that you want to rearrange some of those items later on. Say, decide if price is a significant factor before deciding on color, so with the new DG2 you can just drag the row from position 3 to 1. Now, in the db the items don't get re-ordered. Instead you just put a 1 in the order field for that item (decide if price...), and all previous items are shifted down (actually, you don't even have to do that... with the new dg2 you can just UPDATE each record in the db with "the dgLine of me"). When you reload, you just sort by the "order" field.
It gets a bit hairier when you start introducing the concept of "projects" or "categories" into the list. A list that is already segmented by time. But I'll let you distill that one. Eventually it is hoped this will see the light-of-day in the app Store. But still a ways to go yet. It is a tad amazing how complicated these projects can become.
But a big shout out to everyone here who has been answering my questions. You have really helped in overcoming some substantial hurdles. Very grateful to all of you for the support this community provides.
So, to get back to your idea of using column header sorting. I suppose if the dgOrder field was explicit (it's not) and the category field appeared on the list (it doesn't) you would be able to do it with column heading sorts. However, once you see it you'll realize those items would be both distracting and fairly undesirable. At least I hope I've made the right call.
Mark