If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
#Error appears on subform residing on a tab control
I have two synchronized subforms on an unbound main form and everything
worked great. As you move to each record on sub1, sub2 shows the corresponding records. I needed to add a 3rd subform so I moved sub2 to a tab form and sub3 to another tab and everything still works great. A combobox selection on the main form populates sub1, then sub2 populates with corresponding records to sub1 and sub3 populates with corresponding records to sub2. It's just that now when the main form opens, sub2 shows #Error until sub1 has been populated giving the user the impression that there is a problem. After numerous hours of research, I found that the error only occurs where a subform is linked to another subform on a tab control. Links between subforms that are on the same main form or the same tab control do not display this error. If I move sub2 back to the main form the error goes away but them sub3 displays the error. I was under the impression that there should be no difference in functionality whether a subform resides on a tab control or not. Is this a bug or is there a way to correct this? Thanks! |
#2
|
|||
|
|||
#Error appears on subform residing on a tab control
Don't load sub2 and 3 until sub1 has been populated.
Leave the subforms controls empty, so the form loads without the subforms. Then, after the cbo has been selected, set values for the subform SourceObject property. (david) "John" wrote in message oups.com... I have two synchronized subforms on an unbound main form and everything worked great. As you move to each record on sub1, sub2 shows the corresponding records. I needed to add a 3rd subform so I moved sub2 to a tab form and sub3 to another tab and everything still works great. A combobox selection on the main form populates sub1, then sub2 populates with corresponding records to sub1 and sub3 populates with corresponding records to sub2. It's just that now when the main form opens, sub2 shows #Error until sub1 has been populated giving the user the impression that there is a problem. After numerous hours of research, I found that the error only occurs where a subform is linked to another subform on a tab control. Links between subforms that are on the same main form or the same tab control do not display this error. If I move sub2 back to the main form the error goes away but them sub3 displays the error. I was under the impression that there should be no difference in functionality whether a subform resides on a tab control or not. Is this a bug or is there a way to correct this? Thanks! |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Scrolling text on splash screen | Damon | Using Forms | 20 | November 3rd, 2005 10:37 PM |
set focus to field in another form | Rich1234 | Using Forms | 9 | October 13th, 2005 10:40 AM |
Subform Refresh Problem (but only with an unbound combo box control) | Barry Skidmore | Using Forms | 1 | December 21st, 2004 01:19 AM |
How can I move the focus to a control on a subform? | Brandon | General Discussion | 7 | July 17th, 2004 01:39 AM |
Need help with cascading combos | Tom | Using Forms | 19 | July 1st, 2004 11:11 PM |