Re: Subform cmdButton to Linked Form (?)
- From: Steve Schapel <schapel@xxxxxxxxxxx>
- Date: Thu, 04 Jan 2007 12:04:18 +1300
Tbl,
The functionality you are talking about is handled by Access via the Link Master Fields and Link Child Fields properties of a subform.
A separate form, opened in its own right, has no such connection/relationship with any other form that happens to be open at the same time. Can't be done.
Therefore, you have to explicitly manage all data entered via a separate form. In your example, if you want the ID field of a new record on your "popup" form to be entered with the value of the ID field of the calling form's current record, you can use code to enter it. Probably the Before Insert event of the popup form would be the most appropriate place for this.
--
Steve Schapel, Microsoft Access MVP
tbl wrote:
I guess where I got off-track was in thinking that linked.
forms would function much the same as form/subform, where
it's rather seemless when switching between viewing/editing
existing subform records and creating new subform records.
That's the functionality I was after with my linked forms.
- Follow-Ups:
- Re: Subform cmdButton to Linked Form (?)
- From: tbl
- Re: Subform cmdButton to Linked Form (?)
- References:
- Re: Subform cmdButton to Linked Form (?)
- From: tbl
- Re: Subform cmdButton to Linked Form (?)
- From: Steve Schapel
- Re: Subform cmdButton to Linked Form (?)
- From: tbl
- Re: Subform cmdButton to Linked Form (?)
- Prev by Date: Update record in another table unless it already exists
- Next by Date: Re: Validate field based on Max of the field itself
- Previous by thread: Re: Subform cmdButton to Linked Form (?)
- Next by thread: Re: Subform cmdButton to Linked Form (?)
- Index(es):