Requerying Navigation Subform after Edit

[pcotcamp]

All,



I am relatively new to Access and VBA but have programmed for years in Visual dbase and more recently dBase 8 Plus. The transition has gone very well as I port a legacy 16-bit app over to Access. Until now.

I have been stuck for several days on getting a form to update a Datasheet contained within a Navigation Subform, after I have saved the edits in the form.

Based on suggestions elsewhere, I have tried every possible permutation of form names, NavigationSubform names, bangs, dots, OnClose, OnCurrent, AfterUpdate, events etc. and it still will not work.

To summarize, the hierarchy I am working with is as follows:

1. Main Menu form: Menu-Main
2. SubForm1: NavigationSubform1 (tabbed Navigation Form)
3. Subform2: NavigationSubform2 (tabbed Navigation Form - Contains VendorMain on tab #3)
4. Form: VendorMain - Form containing a Datasheet based on [Vendors Query] with Add /Edit Command Buttons
4. Form: VendorForm (Editing form called by VendorMain's Command Buttons)

**NOTE: I am using overlapping forms and VendorForm is opened as a "standalone" form and not within a subform. VendorForm uses its own query and is not linked to the query of VendorMain. (<--Is this the source of my problem?)

To be clear:

Subform1 is tabbed and contains a second tier of Navigation Tabs. Tab #3 is "Operations"

SubForm2 is also tabbed. Tab #2, "Vendors" contains a link to a form called VendorMain.

VendorMain contains a Command Button called EditButton.

EditButton passes the correct record identifier and opens an editing form: VendorForm.

Upon saving my edits in VendorForm, all I am trying to accomplish is an requery of the Datasheet in Vendormain so that the edits are reflected.

I have tried placing the Requery command in both VendorMain and VendorForm, in every possible Event. All have failed.

The obvious(?) choice would be to place the following in the "Save" button's OnClick event in VendorForm: Forms!Menu-Main!NavigationSubform1!NavigationSubform2.Form.Re query

However, doing so results in an error: "There is no field named Forms!Menu-Main!NavigationSubform1!NavigationSubform2 in the current record."

Can anyone offer a solution? I am at a complete dead-end here.

-Paige


(Please excuse the all-italics. This was copied in from a post in another Access forum.)

[Bob Fitz]

Cross Posted at: http://www.access-programmers.co.uk/...03#post1342803

Please see: http://www.excelguru.ca/content.php?...-cross-posters

[ItsMe]

Navigation Controls are a different animal than, say, a Subform Control. You can access a form in a subform control like this

Me!Subform1.Form!ControlName

I have not had any success finding the fully qualified name of a form that resides within a Navigation Control. In other words Me!NavControl.Form!ControlName does not work. I have tried the form name after the NavControl name etc.

The only thing I have had success with is adjusting the properties of a Nav Control. They have things like Where criteria that you can pass to a form within the Nav control.

[pcotcamp]

Thanks for the input. That makes me feel a little bit better. I thought I was losing my programming mojo.

Nonetheless, is it possible that Microsoft built the tool such that there is no ability to access/control subforms contained in Navigation tabs? Hard to believe.

Unless I am really missing a key concept regarding use of Navigation objects, there has to be a way. I had planned this app to have over a dozen forms embedded in Nav Tabs. Now, all of them are "out of reach"?

Ouch!

Hopefully someone else here can shed some light on either what I am doing wrong or what I am not understanding about the use of Navigation tabs.

Paige

[June7]

Does this help https://www.accessforums.net/forms/t...orm-32053.html

[Xipooo]

Might I suggest you use a Custom Event to handle this?

[ItsMe]

One approach would be to place a click event inside the Class Module of the form that is contained within the Nav Control. As the user interacts with the subform they can fire this Click event. I have done this before and so it is possible. Of course, it does not have to be a click event. It is merely an example. The TempVars is also an example. However, for things like filters you can reference the Navigation control and the Navigation Button that is associated with the form using fully qualified names. That button has properties that will affect the form, like Where Criteria. The button’s properties are available via Fully Qualified Names.

Here is the trick. You have to reference the Nav Control from the form's Class Module. I have not goofed around with them for a while but, if you want to requery the form, you have to requery the control that contains the form (if it is possible to Requery). It may be the Nav Control or it may be the buttons (I do not know and maybe someone else has an actual answer). I would practice with the Buttons Properties and then try moving to a Requery (somehow).

I think the question is how important is the Nav Control to you. I feel it would take Web Forms and interaction with the Back End over a WAN to take advantage of the Nav Control. Otherwise, old school forms are the cat's Meow.