Tab Control Back Color

[wiklendt]

i thought i had tried the subform work-around, however, perhaps i did have a record source set to the form b/c when i tried to put in a subform, the wizard would not let me proceed until i had stated which fields are related. the problem i think is that access uses whatever fields you put in there first as the form record source, without asking whether you want that to happen.

So that must be the answer, to remove the record source from the form :-D i'll try that and fiddle a bit with it when i get the chance.

(as always boB, you manage to point me in the right direction! thanks!)

 

[boblarson]

If you want a subform but unrelated, you can tell the wizard you want to select your own links and then not do it. Or just go to the subform container on the main for an delete the Master/Child links in the properties.

 

[disposablethumb]

...but to control this behavior I remove the recordsource from the subform and assign it to each one via code when the tab is accessed. That way the main form loads fast and the other subforms load when they are needed and not before...

I presume you do this by setting the OnClick of, say Tab 2, to an event procedure that opens a query or otherwise defines the recordset? Examples would be sweet, I'm an awful coder but this sounds great.

-Chris

 

[boblarson]

Actually, the click event of the tab control is poor and something you don't ever want to use. You use the Change event and test to see which tab is selected. I will try to post a sample, if nobody comes up with one before I do, on my website. That's a good idea for another sample.

 

[KenHigg]

I wouldn't say 'don't ever' . It's just that in this case if you clicked on the current page you would be performing needless work. As opposed to the Change event that would fire when you go from one page to another.

 

[boblarson]

Have you tried the click event of the tab? You can't click on the actual "tab" that sticks up. It doesn't respond like you would think it should. The only time it fires if you click on the actual page part of the tab and so by that time you're already on it. The only way to respond to a tab control when you click the part that sticks up like a tab, or if you choose the button view, the button, is to use the Change event of the tab control itself.

 

[KenHigg]

That is screwy. I could only get it to fire when I clicked in the empty space beside the tabs, not even in the big area of the control.

ok - So I don't know what use the click event is any good for (Still I'd rather not say 'don't ever' )

 

[boblarson]

Okay - you're not likely ever going to find a use for it. - there - is that better?

 

[boblarson]

Examples would be sweet...

And a sample is now posted on my website under Access Samples:

http://www.btabdevelopment.com/main/AccessSamples/tabid/54/Default.aspx

 

[disposablethumb]

Just wanted to thank you for your response, I was able to glance over the sample but I'm juggling so many different projects...I know I had questions, but just wanted to take a moment to say thanks.

 

[boblarson]

Just wanted to thank you for your response, I was able to glance over the sample but I'm juggling so many different projects...I know I had questions, but just wanted to take a moment to say thanks.

Hopefully it will help

 

[suepowell]

HI

Just to say thank you to Missingling, often the simple answers are the best.

I couldn't find the backstyle property either, but just that simple statement about selecting the tab object not a page solved the problem and saved loads of time and frustration.

thanks again.

Sue

 

[wiklendt]

(nice hair-cut, boB)!

 

[boblarson]

(nice hair-cut, boB)!

What hair?!!! Where????

 

[missinglinq]

Maybe in your ears? You know how us old code dogs get!