Since there is a known loading order for the tables, a table order via the tool must be performed first to make sure that the sequences are fresh in the backend SQL table(s). Once this is done, manipulation of the backed SQL table(s) can be done, and the correct sequence can be manually put in.
Here are sample SQL equations to work with based on 2 tables being "out of load order" (please adjust the scripts to meet your specific values):
SELECT * FROM
dbo.gtrep_table_order where rto_proj_id = 2346 and rto_pv_id=2360 order by rto_seq_no
Based on the above, we opened up SQL server Management Studio, opened up the Select Statement for the gtrep_table_order table. Ordered it by rto_table so the table names can easily be spotted.
from [dbo].[gtrep_table_order] ORDER BY rto_table
The table order (found in rto_seq_no) was swapped for the two tables of interest. An update was performed on each one of the tables and simply changed their sequence number to the proper number. Make sure and commit the changes if needed with your database.
SET [rto_seq_no] = 25
WHERE [rto_table] = 'SCHED_STASK'
Please make sure and verify the newly introduced table order is correct.