Sub-Sub-Form Saving

[QuantifyRisk]

Presently I have 3 forms: Parent, Sub, Sub-Sub. I have three buttons on Sub-Sub.
1. Save Sub-Sub and add another
2. Save Sub and add another (which includes Sub-Sub)


3. Save Parent (which includes Sub and Sub-Sub)

I have no problem with saving Sub-Sub.
DoCmd.GoToRecord , , acNewRec

However, I am having trouble saving the data for 2 and 3 without overwriting everything. The code is saving the data, then replacing it with null values (because I am apparently telling it to). In my mind, I just want it to erase it so I can enter new information. However, I set each field to Null after I save and that's obviously not a good idea.

Question: How do I save the information, clear out parts of it, but not erase my hard work? Thank you.

[June7]

Move to new record row.

[QuantifyRisk]

How can I get my button to do that?

[June7]

Depends were the buttons are located.

You say they are all on sub-subform?

Need to set focus to form where want to move to new record row.
Review https://www.accessforums.net/access/...red-40057.html

[QuantifyRisk]

What is to be used as a container control?

I added a button to the Sub-Form called ctrAgent and this code to the Sub-Sub-Form button:

Me.Parent!ctrAgent.SetFocus
DoCmd.GoToRecord , , acNewRec

No dice. "Can't move the focus to the control ctrAgent"
I'm not really sure where these pieces should all go.

[June7]

A subform is created by placing a subform/subreport container control on another report. The container control SourceObject can be table, query, form, report.

I always name container control different from the object it holds, like: ctrAgents if it holds the frmAgents.

Code in a subform that dictates behavior of upper forms is unusual. Don't think I've ever tried that. It just might not work.

[QuantifyRisk]

I'm having quite a bit of trouble with this for that reason. Not a lot of help online for Sub-Sub-Forms. However, I was able to screw around with it enough to get this to work:

Me.Parent.Form!ExpirationDate.SetFocus
DoCmd.GoToRecord , , acNewRec

This was on a click() and saved/cleared the record in the sub-form. However, I now need to do the same to the Parent form rom the Sub-Sub-Form. I tried:

Me.Parent.Form!ExpirationDate.SetFocus
DoCmd.GoToRecord , , acNewRec (to save the Sub-Form)
Me.Form!PhysicalZipCode.SetFocus
DoCmd.GoToRecord , , acNewRec (to save the parent form)

Didn't do it. Gave me a 2110 error and said something about the "Main Screen" which is the title of my main menu that loads on startup. Not sure why it went that far.

[June7]

Well, the sub-subform has to go up two levels. So maybe Me.Parent.Parent ?

[QuantifyRisk]

Error 438 for that. I figured I would just go up one level since the prior lines went up one already.

[June7]

The Me refers to the form the code is behind, not the form that has focus. So by using Me, you make the starting point the sub-subform.

[QuantifyRisk]

I tried:

Me.Parent.Form!ExpirationDate.SetFocus
DoCmd.GoToRecord , , acNewRec
Me.Parent.Parent.Form!EstimatedTotalPremium.SetFoc us
DoCmd.GoToRecord , , acNewRec

I know the first two lines work because it clears them out. However, the next two do not. Oddly enough, if I remove the first to, I still get "Error 438: Object doesn't support this property or method". Happens even when I changed to a different field, too. It almost makes me think it's a syntax issue. I may just move it to the Parent form and say screw it.

[June7]

You are doing something I've never tried. According to this http://access.mvps.org/access/forms/frm0031.htm Parent.Parent should work.

[QuantifyRisk]

Microsoft provides this as a help:

There are two possible workarounds for this problem.

• Access the form directly rather than by a variable containing the form.
  -or-
• Create property procedures in the form's code to provide access to the properties of the controls on the form.

Not sure how to do this though. Thanks.

[QuantifyRisk]

Yeah. That site is what I'm using to help but it is just not clicking. I wonder if it's a form property or some other minor issue that's stopping it from working.

[June7]

Sorry, you are on your own from here unless someone else jumps in.