set focus to a subform within a subform within a subform

[n8kindt]

ok, i have a fairly complicated form that goes three forms deep. i've been avoiding this particular dliemma for a while hoping the answer would come to me in a dream or something but i think it's finally time to pose the question. anyone know how to do this? i can set focus to a subform control by using this:

Me.subform1.Form.txt1.SetFocus

but how do i add another subform (or two) to that code? vba doesn't excactly autofill it in so i'm lost.

[puppydogbuddy]

the reference to second nested subform from the main form is:

Me!Subform1.Form!Subform2.Form!ControlName

You can obtain the syntax from this link:

http://www.mvps.org/access/forms/frm0031.htm

[Delerna]

I created a form (frmSubform2) with a text box (Text0) on it
I then created another form (frmSubform1) with a subform (frmSubform2) on it.
I then created a form with a subform (frmSubform1) on it.
In the on load event for the final form I put the following code

Me!frmSubform1.Form!frmSubform2.Form!Text0 = "Hello"
 

and it worked.

[Delerna]

Puppydogbuddy posted while I was posting mine.
:)

[ADezii]

Just as some useless information from ADezii, if you have a Text Box on a Main Form named txtTest, and you wish to set Focus to it from a 3rd Level Sub-Form, namely: Sub-Form1 ==> Sub-Form2 ==> Sub-Form3, you can use the following syntax:

Me.Parent.Parent.Parent![txtTest].SetFocus

NOTE: The Parent Property can be a handy little item to be aware of.

[n8kindt]

ok, guys thanks for your help. unfortunately, i still cannot get it to work. however, after working on it today i realized i had forgotten there is a tab control thrown into the mix so this might be throwing a wrench in things a bit. i've tried for an hour to use variations of the methods you provided but have had no luck. i'll just post my form hierarchy here b/c it seems like the easiest way to explain the situation

frmDRinput > DailyTotals (tab control) > frmReconciling > frmList > txtProductPurchased (text control)

i looked at that table that puppydogg posted and while that has a lot of information, it doesn't say anything about a tab control so i'm still lost here lol. thanks again for your help thus far, guys.

[puppydogbuddy]

i looked at that table that puppydogg posted and while that has a lot of information, it doesn't say anything about a tab control so i'm still lost here lol. thanks again for your help thus far, guys.

Tab control has no impact. See this link:

http://www.mvps.org/access/forms/frm0025.htm

[n8kindt]

Tab control has no impact. See this link:

http://www.mvps.org/access/forms/frm0025.htm

gosh, i don't know what i'm doing wrong then. i might have to post a copy of my project b/c i can't figure out what is going on...

one interesting thing to note is that at one point i had the form 'frmDRInput' name 'DailyReconcilingInputDS'... and when i use the builder tool it always refers to it correctly in the treeview but when i paste the code it uses the old name. not sure if that is relevent or not. i doubt that means it is corrupted... right? anyways, i will look into this situation further and if i can't figure it out i'll just post a copy of my database to see if there is something that i'm not doing right

[puppydogbuddy]

gosh, i don't know what i'm doing wrong then. i might have to post a copy of my project b/c i can't figure out what is going on...

one interesting thing to note is that at one point i had the form 'frmDRInput' name 'DailyReconcilingInputDS'... and when i use the builder tool it always refers to it correctly in the treeview but when i paste the code it uses the old name. not sure if that is relevent or not. i doubt that means it is corrupted... right? anyways, i will look into this situation further and if i can't figure it out i'll just post a copy of my database to see if there is something that i'm not doing right

Sounds like you have the symptoms of the name autocorrect bug. See this link for details on what it is and how to fix.

http://www.allenbrowne.com/bug-03.html

[n8kindt]

Sounds like you have the symptoms of the name autocorrect bug. See this link for details on what it is and how to fix.

http://www.allenbrowne.com/bug-03.html

hmmm it didn't exactly say how to fix it other than turning AutoCorrect off... i actually like it so i don't see this one little bump in the road to be worth turning it off. anyways, i spent some more time at it and still have not been able to solve my problem. here's a sample of my database (i programmed it in access 2007 but i converted it to 2003 so everyone can see it). please disregard the bad naming conventions... this was my first project i ever did in access and now is a small part of a much bigger project

[puppydogbuddy]

hmmm it didn't exactly say how to fix it other than turning AutoCorrect off... i actually like it so i don't see this one little bump in the road to be worth turning it off. anyways, i spent some more time at it and still have not been able to solve my problem. here's a sample of my database (i programmed it in access 2007 but i converted it to 2003 so everyone can see it). please disregard the bad naming conventions... this was my first project i ever did in access and now is a small part of a much bigger project

I have Access 2000....would it be possible for you to attach a sample for version 2000? ....if not, maybe a snapshot?

Also, the name autocorrect bug has proven to be problematic. Strongly advise you to turn it off, but that is your decision.

[n8kindt]

sure here you go. thanks for looking! i will try disabling to see if that does the trick....

[puppydogbuddy]

I reviewed the layout of your forms and subforms.It looks as shown below:

Main Form............subform control.....subform source obj.........record source

frmDRInput........................................ ......................................ActivityLog
............DailyReconcilingInputDS........frmReco nciling...........ActivityLogQuery
............DailyReconcilingInputDS........frmList .......................ActivityLogQuery
............DailyReconcilingInputDetail....frmDeta il....................ActivityLogQuery
............DailyReconcilingInputDetail........... .................................................
.......................SplitPayment.............fr mSplitPayment........QueryTransaction

So what you have are 3 subforms that are children of the main form, and 1 subform that is the child of the third subform. The links that you were trying to reference were the master links of each subform. Consequently, the links will reference the Parents of each child as ADezii noted previously. Will get back to you later.

[puppydogbuddy]

Try these references for your master links. The 2000 version you posted has so many other reference errors (wrong report names, query names,etc.)that I do not have the time to debug your entire application could not test the references below.

Main Form............subform control……....………Master Link………………..

frmDRInput........................................ ........................
............DailyReconcilingInputDS......………………Unb ound
............DailyReconcilingInputDS......………………Par ent. DateSignedIN
............DailyReconcilingInputDetail.………………Pare nt.Parent.ID
............DailyReconcilingInputDetail........... .............
.......................SplitPayment...........………… ………Parent.ID


If you are getting errors on the Date function Date(), see this link. The workaround is to substitute >>>>Int(Now()).
http://bytes.com/forum/thread824120.html

[n8kindt]

Try these references for your master links. The 2000 version you posted has so many other reference errors (wrong report names, query names,etc.)that I do not have the time to debug your entire application could not test the references below.

Main Form............subform control……....………Master Link………………..

frmDRInput........................................ ........................
............DailyReconcilingInputDS......………………Unb ound
............DailyReconcilingInputDS......………………Par ent. DateSignedIN
............DailyReconcilingInputDetail.………………Pare nt.Parent.ID
............DailyReconcilingInputDetail........... .............
.......................SplitPayment...........………… ………Parent.ID


If you are getting errors on the Date function Date(), see this link. The workaround is to substitute >>>>Int(Now()).
http://bytes.com/forum/thread824120.html

oh man puppydogbuddy i am so sorry. i converted the wrong database to 2000 mdb. that's probably why all those links and references were bad... i couldn't get the parent propert to work for my life. HOWEVER, i figured out a major source of the problem. the sub that was supposed to set the focus was called from another sub which set the focus to another control AFTER the other sub was run--effectively killing any focus the sub had just set. so, after i fixed that problem i was able to set focus 3 deep by doing this:

    [DailyReconcilingInputDS].SetFocus
    [DailyReconcilingInputDS].Form![DailyReconcilingInputDS].SetFocus
    [DailyReconcilingInputDS].Form![DailyReconcilingInputDS].Form![ProductPurchased].SetFocus

tadaa! i finally got it to work. once again though, i couldn't get the parent property to work. in fact everytime i tried to add a period after typing in me.parent vba beeped at me as if to warn me i couldn't do that. i'm wondering if you guys misunderstood what i was trying to do b/c everywhere i looked on the web, the parent property was supposed to reference an object that is a parent to the subform. so idk what to make of that. anyways, got it to work--that's the important part. and thank you puppydogbuddy for all of your trouble.

cheers,
nate

[puppydogbuddy]

Glad you got it resolved......and that the original syntax we gave you worked after you discovered the cause of the problem.

[n8kindt]

Glad you got it resolved......and that the original syntax we gave you worked after you discovered the cause of the problem.

i know... sorry to get you all involved with that over a mistake on my part. thanks again for your help.