Form update with new data in sub-subform.

[Degs29]

I've set a control to automatically update certain fields in my main form when I update my subform or sub-subform. This works fine when updating the subform. But when I update my sub-subform, once I update the data and go to new record, it auto-updates the main form, but then sets the focus back on first record of the sub-subform. This is functional, but very annoying. I want the focus to remain on the first field of the new record on the sub-subform.

Anyone know what the cause of this might be?

[Bob Fitz]

You don't say how you

automatically update certain fields in my main form when I update my subform or sub-subform

but if this is done with code in the subforms After Update event, then perhaps you could add one line of code at the end to go to a new record.

[Degs29]

You don't say how you but if this is done with code in the subforms After Update event, then perhaps you could add one line of code at the end to go to a new record.

And that line of code would be...?

Yes, you're right, the updating is done using the sub-subforms After Update event.

[Bob Fitz]

Try:
DoCmd.GoToRecord , , acNewRec

[Degs29]

Try:
DoCmd.GoToRecord , , acNewRec

Nope. It's still jumping back to the first record after the sub-subform's after_update event is complete. I've never seen this before, and assume it has something to do with the form being a sub-subform.

[Degs29]

No one has any ideas how to fix this? Just to clarify, using the exact same method, I can update the main form fields based on the first-level subforms after_update control and the cursor (active field) remains in the correct location. But when I use the exact same method for the second-level subform, the cursor moves to the first record of that subform, rather than staying in the correct location.

I suppose I could ditch the automatic updates, and just use a command button on the main form to manually update the fields, but that's almost as much a hassle as the cursor moving of its own accord.

[Degs29]

Oh, wow! Can't believe this worked. Basically, rather than using a requery to update the fields, I used a refresh of the main form and combine it with the above suggestion and a SetFocus command to get the cursor where I want it:

Forms![Mainform].Form.Refresh
DoCmd.GoToRecord , , acNewRec
Me.[1stfield].SetFocus

If I didn't set the focus of the new record to the 1st field, it would still move the cursor to the new record, but in the last field.

[Bob Fitz]

Nope. It's still jumping back to the first record after the sub-subform's after_update event is complete. I've never seen this before, and assume it has something to do with the form being a sub-subform.

Can you show us your code and tell us in which event it is being used.

[Degs29]

Can you show us your code and tell us in which event it is being used.

I'm using the sub-subforms after_update event.

I had been using the code (With "Mainform" and "Field_n" subbing for actual names):

Forms![Mainform]![Field1].Requery
Forms![Mainform]![Field2].Requery
Forms![Mainform]![Field3].Requery

But see previous post for the solution that ultimately worked. Thanks for your contribution!