Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Changing Subform to Command Button and Cascading Info

Status
Not open for further replies.

davidmo

Technical User
Apr 8, 2003
97
US
Originally I created a form with multiple subforms that were connected by the client's social security number. The connection between the form/subforms worked well and the SSN number would flow to each subform when I inputted into the main form. (Example: When I created a new record and typed the SSN in the main form it automatically went into the subforms. I should mention that each subform is based on seperate tables.)

Due to workflow I had to remove the subforms and instead use command buttons to link the former main form to the former subforms. Now when I type the SSN in the former main form it doesn't flow to the former subforms though I haven't changed the Relationship between the various forms.

The SSN is the primary key in the table that the former main form is bound to.

I have to keep the command buttons but not sure how to link the forms/tables so the info flows/cascades.

Thanks.

DMO
 
I am not quite sure I get you point, but here goes anyway. It is possible to open a form at a specific record:
[tt]DoCmd.OpenForm "FormerSubformName", , , "SSN='" & Me.txtSSN & "'"[/tt]

It is also possible to open a form with an Open Argument, which can then be used to find an existing record, or to create a new one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top