>All I seem to do thse days is write hacks <g>. This problem actually applies to several forms that I'm redesigning and adding fields. In one case, I have around 100 checkboxes being added to two forms, so I have a hack that copies those from one form to the other, and hacks them into the "new page tab" in the other form. It's clever enough to know if the field is already there, in which case it updates it's page location, so that the two forms are kept in sync.
>It also hacks the name of some labels based on the caption, that saves me manually having to change the label name to somethign meaningfull.

You know, you could just have a new pageframe with the needed number of pages, and then copy and paste controls from the pages from the old pageframe in desired order. Note that pasting would put them at a slightly offset position, but you could nudge them back into proper position using arrow keys (I think 8 pixels up and left).

>However, I'm not sure how field order is determined on a tab, is it just the physical order of the fields in the .FRX ?

In the .scx, but no, that's instantiation order that depends on their recno() in the scx. It's the .TabOrder property that you need... which is probably set at the time you insert them. You can set that in the PEM sheet, but with a hundred of them, you may better use the interactive tool we have at hand: you need to select anything inside the page (aka tab - but purists here would say that tab is the widget that holds your page's caption) and then on your standard toolbar click the Tab Order button, and there you can set your tab order as you like.