Question first: Is there the equivalent
Ok, now for some context:
I’m Playing with the new “Navigation Control” that MS has so happily supplied to replace the “outdated” switchboard and yet they have only provided the psionic version of the information as to how to exactly use this control… and a few short adhoc pieces (( Build navigation UI with Access 2010 )) that make it seem like a seamless drag and drop.
I like the design, I don’t like some features, and transferring information from one form to the other sucks as the forms are closed and reopened (sort-of late opening forms in a tabbed parent to speed loading) so referring to the calling form’s controls is not possible; however, that’s another issue that might be solved.
So……. I’ve run in to a bit of a nuisance (as alluded to in the question): in order to get the forms (or reports) into the new Navigation Control… it appears that you have to build the form (report) first then drag-n-drop onto the new control!
Thus, I go thru all of the trouble to design a form that works nicely as a stand-alone implementation. In that form are several cascading combo-boxes. Nothing unusual about this, I’m sure many of us have done so… and I drag this form into the new “Navigation Form.” However, all of these little CBO have as a record source a query that has a parameter like this
This gets even worse if there is a subform on the form that I just dropped onto the Navigation Form….
Now the VBA in this form works just as I have programed… no issues. The reason the code works is that most of it either deals with the recordsets or has things like
In anycase we're back to the question: Is there the equivalent
[ME]![SomeControlName] that can be used in the form control’s recordsource parameter such as in a combo-box?Ok, now for some context:
I’m Playing with the new “Navigation Control” that MS has so happily supplied to replace the “outdated” switchboard and yet they have only provided the psionic version of the information as to how to exactly use this control… and a few short adhoc pieces (( Build navigation UI with Access 2010 )) that make it seem like a seamless drag and drop.
I like the design, I don’t like some features, and transferring information from one form to the other sucks as the forms are closed and reopened (sort-of late opening forms in a tabbed parent to speed loading) so referring to the calling form’s controls is not possible; however, that’s another issue that might be solved.
So……. I’ve run in to a bit of a nuisance (as alluded to in the question): in order to get the forms (or reports) into the new Navigation Control… it appears that you have to build the form (report) first then drag-n-drop onto the new control!
Thus, I go thru all of the trouble to design a form that works nicely as a stand-alone implementation. In that form are several cascading combo-boxes. Nothing unusual about this, I’m sure many of us have done so… and I drag this form into the new “Navigation Form.” However, all of these little CBO have as a record source a query that has a parameter like this
[forms]![frm_customeracc ounts]![zcbo_newcustome r] that goes in the WHERE clause so as to set-up the record source based on the prior CBO. and ofcourse, as with any sub, these now require that I go in and change them to something like this: [forms]![NavigationForm]![NavigationSubfo rm].[Form]![zcbo_newcustome r] once the form is dropped onto the “Navigation Control.” This gets even worse if there is a subform on the form that I just dropped onto the Navigation Form….
Now the VBA in this form works just as I have programed… no issues. The reason the code works is that most of it either deals with the recordsets or has things like
me.z_somecontro l.value = z_some_data_for _control so no problems with the VBA side of things… yet.In anycase we're back to the question: Is there the equivalent
[ME]![SomeControlName] that can be used in the form control’s recordsource parameter such as in a combo-box?
Comment