Well, I think there is a reason you do that, only remove the code, if the textboxes and labels are by default enabled.
You may have based your form on some of the FFC classes that include a navbar and an editmode, which start with controls disabled or readonly. But you may do this enabling too early, because that navigation mode / not editing mode is what the form starts with, but might be set up after you already enabled all controls.
If you show your button code to statr the form, there could be more said, also please tell us where that setall() code is. With THisForm (if it is that) suggests this code is within the form started, so it's happening no matter from where you start it. You would need to find out the reason it is done in one case and not in another. I recommend single stepping in the debugger to see what happens in all the events that are happening at form start, that's not only load, init, but also might include the show method and the gotfocus of the control with taborder 1. And there could be code overriding all you do with your setalls.
And last not least, as Mike also already addresses the enabled property controls whether you can set focus to a control and edit it's value. It's not controlling the visibility of controls, that's done by the visible property. A readonly state also is better for allowing users to not only better read with more color contrast - the controls are not greyed - you also can set focus into them, select and copy text.
Chriss