Trying to get second level subform to act like split form

[Pbear88]

I’m trying to get a second level subform to act like a split form (where you click (or double click) a datasheet view and it brings that record to the current details view. I have a main form (MainInjuryForm) that has a Subform (InjurySubForm). They are linked Parent-Child with PatientID. There is a PatientInfo Table and an InjuryTable that has a one-many relationship.
The InjurySubForm is a single record view, but I have also added another subform (InjuryHistoryForm) that is a datasheet view within the InjurySubForm. Those two subforms are also linked Parent-child with PatientID (just one with a single form and one with a datasheet form). I want to be able to click on a record in the datasheet view and have it bring the details to the current view of the InjurySubForm. The field that should be dependent on this action is the InjuryID field, since it is the main identifier in both subforms. Is this possible with this structure? MainForm
Subform1
Subform2

[CJ_London]

Think I have got this right. You have

MainInjuryForm>InjurySubForm>InjuryHistoryForm

1. if so, it would be better to go

MainInjuryForm>InjuryHistoryForm>InjurySubForm

and make your InjuryHistoryForm a continuous form and put the InjuryHistoryForm in the header or footer. You may get a warning, but just ignore it


2. if you want to stick to your layout, try the following - not tested so not sure it will work

a.make the child/master values for the InjuryHistoryForm subform control PatientID

b. in the InjuryHistoryForm current event put

me.parent.filter="InjuryID=" & me.InjuryID
me.parent.filteron=true


3. Another alternative is to have both InjurySubForm InjuryHistoryForm as subforms on your MainInjuryForm

a. Then on your MainInjuryForm have a hidden control called say txtInjuryID

b. make the child/master values for the InjuryHistoryForm subform control PatientID
c. make the child/master values for the InjurySubForm subform control InjuryID/txtInjuryID respectively

d. in the InjuryHistoryForm current event put

me.parent.txtInjuryID= me.InjuryID

[Pbear88]

Thanks Ajax. I tried the 2nd suggestion, but it didn't work. On running the Mainform, it would ask for a parameter value for "sFilter". When I clicked ok, the records on the InjuryHistorForm would blank out.

I'll try your 3rd suggestion next.

[Pbear88]

Ajax, the 3rd suggestion worked for the current records. But now when I'm trying to add a new record through the InjurySubForm, it doesn't assign the new record a value for the PatientID field in the InjuryTable. Any suggestions on how to auto populate that with the new child/master settings that we now have established?

[CJ_London]

would ask for a parameter value for "sFilter".

Think you must have spelt filter wrong

Any suggestions on how to auto populate that with the new child/master settings that we now have established?

linkchild/master properties can have more than one field

cant remember what the separator is, either a comma or a semi colon, so something like

linkmaster - patientID;txtInjuryID
linkchild - patientID;InjuryID

If that doesn't work, go back to version2, think you just had a typo

[Pbear88]

Thanks Ajax,

Version 2 worked. I still had a Filter in the properties that I forgot about, when I was trying to figure this out before my initial post. Thank you so much, again! I'm sure I'll be back. It's a pretty extensive project that I'm trying to work through, but a great learning experience.

[Pbear88]

Just ran into a secondary issue with Version 2. Once I click on the datasheet subform and the current record is displayed in the single form(details) view, I would like the clients to have the ability to edit the current record that is displayed. I created a button and in the event procedure for the OnClick method, I put in the code: Me.AllowEdits = True. Now, when I click on the button, it jumps to the first record instead of the current record that was displayed. What do I need to add to the button to make it stay on the current record that I have chosen to be displayed in the single form(details) view?

Thank you for any assistance.

[CJ_London]

In short I don't know, I would have used option 1, in which case it would not be a problem. Option 2 was untested and could well have problems once you move from the original 'brief'.

My guess would be that by changing the allow edits property, you are disabling the filter. So you would need to reenable it after changing the property. this might be something like copying the me.filter property to a temporary string, changing the allowedits property, then copying back afterwards and setting filteron, or might just mean setting filteron. You'll need to experiment.

An alternative might be to set all controls locked property to true, then setting them to false when the button is clicked.

[Pbear88]

Ok. Thank you. I'll try your suggestions tomorrow.