One thing I notice is when you use the comma for the actual sort, it will use whatever is after the comma, example.
Brooks, Garth & Trisha Yearwood - this is VERY common among the database listings. HOWEVER if you want to list it as first name last name, it will list as
Garth & Trisha Yearwood Brooks. This one you HAVE to edit as
Brooks & Trisha Yearwood, Garth in order for it to read
Garth Brooks & Trisha Yearwood. There is no other way around it. And if there are more than 1 comma in the line ie multiple artists then it really messes the line up if you want it First name Last name. If you could fix this to truly work, that would be great, however the only workaround I have found to work is actually editing all the artists.

As long as it doesn't force the sort where it HAS to alphabetize with the first name. I want Trace Adkins to list as Trace Adkins under A - NOT T.

Admin
personally i think the batch edit would be better !

Agree!

KJ File Manager does that, but not for KMA files :f

All we can do is to went on their site and asking them to support KMA files.
That would be a must for us Hoster users.

They let me know that they will support KMA files if there are enough people asking for it.

So go on and let's do it!

Sweet! Thanks, that will save me huge amounts of time, as well as everyone else I am sure. Thanks!!

We have an engineering problem. :e :s

Since the Artist fields contain both last and first names, we do not have sort access to order them by first or last name as I proposed above. To accomplish this would require building an array in RAM then running a sort on the [last], [first] fields within the [name] field.

After evaluating this from the code level, this turned into a "large" project that we cannot justify at this time. I've got it in our spec to do when we get a break.

Vista set us back about 6 months this year so we are still playing catch-up. We could work in a "small" project, but this is not in that class. :s