I have a wierd problem. This works sometimes but not always.
I know, I know I have a bad naming convention as well.
I have a form that has a subform on it. The subform has 7 subforms on it. The problem is this:
On the main form I have a text box with the control source set to:
=[child10].form!text10
Text10 is on the first subform, its control source is:
=[child1].form!text2+[child2].form!text2....
(child1,2,3,etc are on the form child10)
When I open Child10 alone I see the value in text10. When I open the main form and have child10 visible I still see the value displayed on child10 but not in the text box on the main form. The text box on the main form shows error.
Now to make it work, I right click in that text box and go to properties. If I the change anyother text boxes control source to anything then the value pops up in the textbox with the error. I can save that then re-open the form and I am back to an error. For the time being I have gotten around this. I am just wondering what the issue is? I think it has to do with a control referencing a grandchild. Is this correct? If so why does access have issues with this? Is it syntax?
I know, I know I have a bad naming convention as well.
I have a form that has a subform on it. The subform has 7 subforms on it. The problem is this:
On the main form I have a text box with the control source set to:
=[child10].form!text10
Text10 is on the first subform, its control source is:
=[child1].form!text2+[child2].form!text2....
(child1,2,3,etc are on the form child10)
When I open Child10 alone I see the value in text10. When I open the main form and have child10 visible I still see the value displayed on child10 but not in the text box on the main form. The text box on the main form shows error.
Now to make it work, I right click in that text box and go to properties. If I the change anyother text boxes control source to anything then the value pops up in the textbox with the error. I can save that then re-open the form and I am back to an error. For the time being I have gotten around this. I am just wondering what the issue is? I think it has to do with a control referencing a grandchild. Is this correct? If so why does access have issues with this? Is it syntax?
