If your database is not very dynamic you could sort your records by creation date descending, export and import in a clone.
Relate to, or find, the records you want and then sort them.
Sorting is very important in a paper filing system, and when performing a particular task. For just storing your data, the order shouldn't matter, and FM will always just append new records to the end.
Generally speaking, if you have a process that involves the user, or a script, sorting every record in your table and then looping or scrolling through it, you're not really getting the most out of your database. Relate to, or find, the (limited) records you want and sort them as is appropriate for the process at hand, either with the sort command or by sorting the relationship or portal.
This may seem like a personal preference, or even a peeve. It's both, due to experiences getting caught up in this assumed requirement before, and the experience of the ease that came from discarding it and letting storage happen in the order that it does. However, if you need more ammunition for this, check out the Wikipedia page for first normal form, towards the end: First normal form - Wikipedia, the free encyclopedia
It can be done in SQL query with ORDER BY clause, and FMI should be easy to implement it in option of "find records".
I think the feature didn't get enough request, and they have many things to do before making 2 steps into 1.