Yesterday I spent most of the day trying to sort out this problem on the project I'm working on.

We are using farpoint tab pro, as It is alot better than the standard tab ocx.

I had a form that had several sub forms inside each tab. Each sub form is contained inside a frame. Because of business rules the sub forms have to be enabled and disabled. So I did the usual frame.enabled = false. ran the project and as soon as you change tabs, the frames become enabled again. I spent a good part of yesterday going through my code with a fine tooth comb trying to find out why they got enabled again. If I tryrd dissabling an individual control, it worked fine, just not the frames. Turns out that the tab control has a method called setChildenabled, and using that, it works fine. This probably means the muppets at far point who made this, made the ocx and realised this problem and put in the method as a work around. Why can't people develop properly, especially when they are charging £60 a throw for this control.

RIght that's my sulking done for the day