Embed A Navigation Form Instead Of Using Tabs (navigation Form As Subform)

[jerem]

Hi,

Is that at all possible? I thought it would be a good idea if I have a form with a lot of data structured in tabs. Since the tab loads all the data at once while the navigation form browses to the desired form. I have tried but the issue is the Master-Child link. The form in the navigation form is not considered as a subform, hence, no way to set a Master-Child link. The navigation form itself is the subform but even when setting up a link there it has no influence on the form displayed by the navigation form.



Any idea how this could work or is it just that it is not meant to be used this way?

Thanks
Jerem

Cross:
http://www.utteraccess.com/forum/Embed-Navigation-Form-t2023073.html
http://www.access-programmers.co.uk/...06#post1390206

[ranman256]

I have been using master-subform method a long time and they work just fine.
If you use tabs, use only 1 subform and swap out data as you pick a tab. To prevent out-o-memory issues.

[jerem]

If you use tabs, use only 1 subform and swap out data as you pick a tab.

Can you explain how you do that?

[jerem]

Alright... I had an answer on another forum. The technique seems to be to create a single subform, add a tab control, send it to back so that the subform is always visible and then change the source based on the tabs.
Sounds cool! I'm going to give it a try. Thanks.

[June7]

Wouldn't need a tab control for that. Regular command buttons can accomplish the same.

I've never used Navigation form, don't like it.

I guess if need a dependent child form on Navigation form, its RecordSource would have to be a dynamic parameter query that references control on main form for the criteria.

[jerem]

True that command buttons would be just fine in this case.

[jerem]

I haven't tried yet but does that mean that if a master child relationship exists, it would have to be set up each time the RecordSource changes?

[June7]

Do you mean for the conventional subform?

If all the child tables have the same FK field name for the master PK, then don't have to change the subform container Master/Child links properties. If the field names are different, then yes, must change the Child link property when changing the subform container SourceObject property.

[jerem]

Ok... I guess it makes sense.

[June7]

Options for the Child link key to avoid code to change the property:

1. same field name in the child tables

2. subforms have a query as RecordSource, construct a field in the query to serve as the child link, use the same alias name in each query
AliasName: [the actual fieldname]

[jerem]

I got it the first time sorry... Non-native English speaker mistake: what I meant was of course, it's just simple and makes a lot of sense.

[June7]

I got it that you got it about having to programmatically change the link property if field names are different. Just offering options to avoid that, in case they hadn't occurred to you.

[jerem]

Ok thanks! It helps a lot.