Page tabs keep going AWOL

[Guest]

I have a form with 5 page tabs at the top.

In design view they appear ok, but as soon as I go into the normal view the
user sees, they disappear and I can only reshow them by pressing
CTRL-SHIFT-TAB.

Can someone please help?

Thanks
Phil

 

[Allen Browne]

How do you have the Style property of the tab control set?

Or is the Height of the (Detail?) section of the form inadequate?

 

[Guest]

Thanks for your reply. I'm out of office today but wil get back tomorrow.

Thanks

 

[missinglinq via AccessMonster.com]

I'd like an answer to this mystery also! I have an app with tabbed pages and
everything works fine when the form is invoked from the Objects Dialog box or
when invoked from another form. The behaviour he's referring to (I think)
occurs when you're in Design View and then run the form firectly from there.
The Tabbed Pages disappear and the lower half of the form blanks out.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000

Message posted via AccessMonster.com

 

[Guest]

Yes, that's exactly it.

Infuriating, as this is the only thing preventing us releasing the previous
6 months' work!

 

[Guest]

Style prop = "Tabs"

Height looks ok!

I don't mean to sound cheeky, but would you mind if I emailed you my
database pls? Sorry if I'm causing offence, but I genuinely can't understand
what I'm doing wrong.

 

[Allen Browne]

Before you email me, can you do a couple of things.

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html
Then Compact the database:
Tools | Database Utilities | Compact/Repair

2. Make a copy of the database (so you don't damage your original.)
Open the form in design view.
Set the form's HasModule property to No, answering Yes to the confirmation.
Save and close the form.
Compact the database again.
Does the form still play up without any code?

3. Export the form to a text file, using the undocumented SaveAsText.
This kind of thing:
SaveAsText acForm, "Form1", "C:\Form1.txt"
Then delete the form, and compact the database.
Now import the form again from the text file:
LoadFromText acForm, "Form1", "C:\Form1.txt"
Did that rescue it?

4. If it still plays up, try the divide'n'conquor trick.
Delete half the controls from the form. Compact.
Does it still play up?
If so, delete half again, and so on.
Is there a point where it comes good?
If so, add in half the things from the last delete, continuing until you
pinpoint the culprit.

I'm really under the hammer at the moment, Phil, but if that goes nowhere
you can email me and include the text of this thread.

 

[missinglinq via AccessMonster.com]

Granted this is aggravating, Phil, but since it only appears when going from
Design View to Normal View, I don't see why that should hold up deploying the
apps. End users aren't usually granted access to Design View, and this is the
only way I've experienced this particular snafu.

BTW, I've gone thru all of Allen's suggestions without success.

 

[Allen Browne]

You killed the code, exported with SaveAsText, and reimported, and the
problem survived?

 

[Guest]

Hi chaps,

I solved it thanks to Allen.

The problem was in Normal View, the tabs weren't showing so it couldn't be
deployed in that state.

Basically the problem was two of the six pages were too long. When I
shortened these pages, the headers show ok!!

Hoorah, what a result, at last this problem has disappeared!

Many thanks chaps, and especially Allen I really appreciate all your kind
help.

Cheers
Phil

 

[Guest]

To be honest, t'was merely down to resizing the forms.

The code thing had no effect, sorry.