You probably shouldn't be relying on Sesame to maintain the order of the subform records based on the order that they were entered. You really should have a field that you can sort by. Then, you don't need to be concerned with the order that they export/import, because you will sort them anyway.

Here's an example of what I did to resolve this...

I have an invoicing application in which I have a line item subform that details the work performed. This subform has a date field, but I didn't want a date on every line. I just wanted each date to appear only once -- a single line to include the date and labor charges, then a line (or lines) below that which detail the materials. The materials lines do not have a date filled in. Each successive date and labor line is followed by the material used on each of those dates.

There was no way to be sure the materials line(s) would always fall into place below the date for which they belonged. So, I added another field that is simply titled "Sort". This field contains numbers corresponding to the position for which each record should appear in the table view subform. This way, I can simply have a default sort attached to the subform, and my line items are always displayed in the proper order. So, I get a line with a date and labor, followed by the materials lines, then another line with a date and labor, followed by more materials lines, and so on.

I don't worry about entering the numbers into the Sort field. Programming takes care of that for me.