when you call your second form do.
formblah.show vbmodal

then call your function right after that statment.

vbmodal will hold exectuion of the parent window while the child window is open. This is why you can retrieve the value as the next statment in your code.

Greetings.
Thanks for the input.
Hey, it works! Hooray! Thanks.

Glad to be of assistance :p

Greetings.
You are indeed of great assistance.
By the way, regarding the Private Sub Form_Activate(), is it true that it is better to store initializations there instead of Private Sub Form_Load()?
I remember I've read somewhere that it is more efficient to store into Form_Activate().
What's the difference?

I'm trying to solve this problem - passing data between 2 forms. The 2nd Form has to take a value stored in a String from the 1st Form.
I have made the String variable in the 1st Form as Public. At the start of execution, it works fine. When I press 'Back' on the 2nd Form, I go to the 1st Form. There I insert a different value & when I click to go on to the 2nd Form, it takes the value from the previous value. At the 3rd try, it takes the value that I have inserted during the 2nd try as if it is slowed down by 1 step. LOL. I can't figure out which is wrong.
Is it because of the Load form2 & Unload form1 sequence of execution?
Please advise.

#1: the only diffrence between the 2 is form load, gets called every time you call Load formblah, while Form_Activate gets called every time you do formblah.show. that's the only diffrence.

#2 create a public function in a module, also if you wish to pass data between the 2 create the public variables you need outside the fucntion. then have the function call the second window formblah.show, vbmodal. right before you exit this window make sure you dump any information you want shared into the public variables you have created. when control is passed back to the module you then make your function return the value of the public variables!

Greetings.
#1 : Got what you meant. Thanks.
#2 : Not sure if I fully understand. But, I'll give it a try and return with questions if I'm stuck.
Thanks a lot.

haha, I didn't think so... its really late for me, and my mind is half shutoff. (2:35am) Ill repost again tom with an example and explain it better.... goodnight!

Greetings.
Woah, it's really late, dude. Good nite!
Thanks for the effort. Looking forward to gain something from your lecture tomorrow. :-)

Greetings.
Bringing back an old topic.
But not dialog box this time around.
Same problem: passing variables between forms.
Issue: Form Load & Unload.
Previously, without proper testing of each and every cases, the output was like what I have expected, so I thought I would have no problem.

[1] Again, on the arrangement of Load Form1 vs. Unload Form2
Initially, I thought it doesn't matter but not until I found that it actually matters!
I realise that when I put Unload Form1 before Load Form2, I would not be able to
use the Public variables in Form1. And so, I placed Load Form2 before Unload
Form1.

The problem arises here when I did step [1]. I load Form3 from Form2. I deem that the error occurs because although in Form2, I have Load Form3 followed by Unload Form2, when Form3 is showed Form1 & Form2 is still loaded in the memory because everything goes in a sequence:

Load Form1

Load Form2

Load Form3

Unload Form3

Unload Form2

Unload Form1

Actually, the real scenario goes like this:
Forms: Form1, Form2, Form3.
Form3 can be loaded by Form1 and Form2.
Therefore, in Form3, I'd like to code for different activities for different form that loaded Form3. How can I achieve that?
I did ->
However, I realised later that this is not right, because when I clicked on the navigation menu on the left hand side of the form to go to Form2, then Form3, it works fine. Continue with clicking on Form1, then Form3 -> output was not as expected, because, it doesn't go to the ElseIf all the time when at the beginning Form1.cmdGo is evaluated True. :-|
Sorry, I know it's a bit confusing there, but I hope someone would understand my problem.