access tab control, all subforms (3) change to 1st one added

[Guest]

In Access 2000, I am created a form with a tab control. The first tab has 1
subform, the 2nd tab has 2 subforms. When I save the form, and open it back
up, all 3 subforms are the same (the one I put on the first tab). I change
the two subforms to the correct forms, save it, open it again, and they have
changed back to the same subform on the first tab.

 

[John Vinson]

In Access 2000, I am created a form with a tab control. The first tab has 1
subform, the 2nd tab has 2 subforms. When I save the form, and open it back
up, all 3 subforms are the same (the one I put on the first tab). I change
the two subforms to the correct forms, save it, open it again, and they have
changed back to the same subform on the first tab.

I strongly suspect that the "first" subform is IN FRONT OF the tab
control, not actually "on" it. It's concealing the contents of the
other pages.

This is a pretty easy error to make, but it's not hard to fix. Open
the Form in design view; select the Subform; type Ctrl-X to cut it to
the clipboard. Then select the desired tab of the tab control, *by
clicking the tab itself*, not the surface of the page - the entire
page should darken to indicate that it has been selected. Type Ctrl-V
to paste the Subform control onto the tab page itself.

You may need to do the same for the other subforms as well, onto their
own pages.

John W. Vinson[MVP]

 

[Guest]

Nope, that is not the problem.
The 3 subforms are in different locations on the 2 tabs. I can open the
form, correct the subforms, and it works until I save and close the form.
When I open the form again, it is back to displaying the same subform in all
3 locations. When a subform is placed on a form, there is a title placed
just above it - those do not change.
I was also getting the "Error connecting to file. Network connection may
have been lost" error message at this site when I copied a form with some VBA
code from one database to another.
They are in the process of upgrading to Access 2003, so I am hoping these
quirky errors will go away when that happens.