I took some time this morning to investigate WinSPM a bit further.
First, I added several new sites. No matter their name, they appeared on bottom of list. Site.db was opened in Paradox and table was sorted on "Available Sites" name. WinSPM launched again, names appeared in alphabetical order, but any new site added went to bottom of list.
Next, Site.db was restructured within Paradox. SiteName field was moved from second position to first position. New sites were added in WinSPM but they still did not automatically re-sort into alphabetical order.
Next, I restructured Site.db by placing an index key onto SiteName since it was now the first field in the table (this is required in Paradox).
Now when adding a new Available Site within WinSPM they immediately resort correctly. So far there has been no problem and I don't expect any as table data was not changed. WinSPM uses the SiteID to link to other tables for data retrieval, but since none of those tables seem to be keyed, does not object to Site.db being keyed on SiteName. Of course, before one starts monkeying around with file data one *always* does a backup, just in case.
Your (or your customers') mileage may vary, etc. I caution anyone to NOT make changes in table data (i.e., SiteID number) as the data is linked to other tables (i.e., Notes and Reports). Links will be broken and you will have to re-enter your sites, print out all those Notes and Reports you had, and who knows what else.
I am not familiar with Access. Maybe someone will give it a whirl as it is much more available than is Paradox.