Putting ** is not a good way to do this.
on 2 counts:-
* is a wild card character in searches and so is not easy to search for.
I am not sure you really want ** to appear on the account names either, looks untidy.
What I would do is to use a Searchable field to tag the customer types.
Candidates would be the
Account Status field I could have an account status for each type
The Terms Fields, text or number of days might work
One of the three analysis fields
Then I can use a search in the customer ledger to get me groups of each type customer, saving the searches so I can load them up next time I need them (and for use for other purposes).
With the 30 day customers selected with the search I could run the Aged report on screen, or use the one in reports to list them.
If you wanted to be fancy you could add extra criteria to this search to limit it to customer that are "overdue" ehn you are chasing, if you have a look at the credit control guide it explains about using criteria in a bit more detail.
http://support.makingithappen.co.uk/sag ... ontrol.htm
I could then select the 60 day customers and do the same thing.
------------------------
While we are here this is the low down on report sorting.
The sort order in the report is determined by the structure of the report the header/footer groups and then within those groups by the sort order.
Users often add sorts and don't know/think about the grouping structure so get tripped up by this.
What you need to do in these circumstances is to add a header/footer group outside of the existing one, so that the structure groups things the way you want rather than sorting them within the existing groups. when you add a header/footer group you might not even need to print them, they are only needed for structure.
If you look at the Aged Debtor Report you will see that the structure is to have a group header/footer for each Account Ref. What you would need to do is to change the structure so that rather than using Account Ref it used the Account Name, this would give you a group for each account name.
Note: 2 accounts with the same name would also be grouped by this and merged together, if you didn't want that to happen, then you should add the name as an additional grouping outside the account ref, so it would be grouped by the name and then with each group of names each account ref would be printed, the headers and footer for the name group could be hidden because you don't really need to see them.
I think this might be a bit irrelevant because my earlier suggestion will probably work better for you.