We have seen that in our running applications that childtable populate is very slow compared to pre-TD7 applications.
Simple testcases to compare the TD versions did not find the cause until now !!!

We have found that when a dialogbox is open, all childtables in the application, even located on different forms, will populate data more slowly. This impact is for each running dialog instance.
So having 2 dialogs will decrease populate performance more. Having more and more dialogs will in the end make childtables so slow that it is really unusable.

See testcase:

Run the sample

Enter the total number of rows to populate in the table (5000=default)

Press EXECUTE

See the timing result in the datafield (in milliseconds)

Now press the Create dialog button. It will create a simple modeless dialog without childs and any code.

Redo the testcase by pressing EXECUTE.

See that the time has increased to populate the table.

To see the impact, press Create dialog button many times to have multiple dialogs present in the running application.
See that for each dialog added, the performance decreases more and more.

I tested it in TD 7.0.2 and the 7.0.3 beta and both versions show the issue.

The testcase is saved in TD61 format so can be tested from TD61 up to TD70.

ChildTable_Dialog_Issue_TD61.zip

You do not have the required permissions to view the files attached to this post.