Form_Activate

[khann]

hi...i need some help regarding Form_Activate...

here goes...
see, i have this form form1(mdichild=true)...it is open or its is visible..then i open another form form2(mdichild=false) and do some processing,after i close form2...form1 is still visible but it will not pass to Form_Activate event anymore...i need to re-initialize some variables in form1....any ideas how to do it???

thanks a lot...

[JordanChris]

Use the Form_GotFocus routine

[khann]

hi JordanChris...

i already did that..still nothing happens...i even use Form_Paint()...thanks for your reply nywys...

[Hack]

Put what you need to reinitialize in a Sub Routine. Call it when the form loads, and call it again when you need to redo stuff. Make sure the Sub is Public so it can be called from a different form.

[Frans C]

I think the MDI parent will get the activate event.

[IROY55]

This is all you need to do:

'Form2 - non MDI child
Private Sub Form_Unload(Cancel As Integer)
    Form1.SetFocus 'set focus back to MDI child form
End Sub
'Form1 - MDI child
Private Sub Form_Activate()
    Debug.Print "Form1.Activate"
End Sub

[Wokawidget]

Don't use MDI forms...They suck like small squirrels riding tandom on a used turnip...

[IROY55]

Don't use MDI forms...They suck ...

It's not about what we like but what business needs.

[Wokawidget]

Business does not know what it needs...The majority of the time, the user hasn't got a clue what they want, or what is on offer. 90% of the time a customer has asked for something and I have offered an alternative, which they have agreed is a better way than theirs...
MDI forms, Multi Document Interfaces, and designed exactally for that tpye of project. A project that has many of the same type of document open, ie word 97...One MDI form can control loads of word documents. In this situation MDI forms are great. But when trying to write an app that has many types of forms and displays, MDI forms are just plain crap, and should not be used for these types of applications.
I have no idea why people use MDI forms for non MDI applications. It just makes no sense!
To be a good programmer you have to know what is the right control, code, references for the job...for some strange and bizzare reason, people continually use MDI forms...and then run into trouble. Menu's are a cracking example, and the reason being is that an MDI document shouldn't have menus All the tools/function or any other menu should be on the MDI form and Not in the child document...

Woka

[IROY55]

You are totally wrong on this: serious applications (not to mention interfaces) are design by architects and often according to a very serious analisys done by a group of analysts. Developer may dissagree on some issues wich may or may not be taken into considerations but it all depends on the entire picture wich isn't necessary of our (developres) business.

[Wokawidget]

I disagree...serious applications? What do you class as a serious application? One that controls the state and production of a million pounds worth of GaAs wafers, for military and satalite communications, as it goes through different processes? If so, then the apps I write are very serious. I make a mistaken then oooops, I've just cost the company one hundred thousand quid...

[IROY55]

Woka,
you have your opinion wich (unfortunately for you) I can't change it. So let's stop this chit-chat.

[Wokawidget]

Wasn't having a go or anything, was just trying to put my point across, which, if you haven't guessed already, I am sticking too
No offence meant
If MDI forms had more features, or if they were easier to use, or didn't restrict your coding in anyway then I would use them more often as they do have some benefits, just not for SDI applications...

me

[khann]

Originally posted by Hack
Put what you need to reinitialize in a Sub Routine. Call it when the form loads, and call it again when you need to redo stuff. Make sure the Sub is Public so it can be called from a different form.

hi hack...thank u...

[khann]

Originally posted by IROY55
This is all you need to do:

'Form2 - non MDI child
Private Sub Form_Unload(Cancel As Integer)
    Form1.SetFocus 'set focus back to MDI child form
End Sub
'Form1 - MDI child
Private Sub Form_Activate()
    Debug.Print "Form1.Activate"
End Sub

hey roy..ill try this... ..thanks

[khann]

Originally posted by Wokawidget
Business does not know what it needs...The majority of the time, the user hasn't got a clue what they want, or what is on offer. 90% of the time a customer has asked for something and I have offered an alternative, which they have agreed is a better way than theirs...
MDI forms, Multi Document Interfaces, and designed exactally for that tpye of project. A project that has many of the same type of document open, ie word 97...One MDI form can control loads of word documents. In this situation MDI forms are great. But when trying to write an app that has many types of forms and displays, MDI forms are just plain crap, and should not be used for these types of applications.
I have no idea why people use MDI forms for non MDI applications. It just makes no sense!
To be a good programmer you have to know what is the right control, code, references for the job...for some strange and bizzare reason, people continually use MDI forms...and then run into trouble. Menu's are a cracking example, and the reason being is that an MDI document shouldn't have menus All the tools/function or any other menu should be on the MDI form and Not in the child document...

Woka

hey there.. ..
well..i think i really need to use mdichild..coz my users want some modules .. like 2-3 modules open simultaneously...they just use minimized..maximed to switch from one module to another which i cannot do when my form is in vbmodal(they want to eliminate the extra trip on menu)...but then i need other forms to be in vbmodal so to save necessary information before returning to main/calling form...
i guess if ill be the one to decide..ill make it simple as much as possible..who wants to run into trouble anyway...but i have my users...and i guess its my job to do what they think would be easier for them...thats whats automation is all about...i think..
...thanks for ur opinion anyway..ill keep it in mind...

[Wokawidget]

No probs

MDI forms are just a pet hate of mine...a HUGE pet hate

Hope it works ok..

Woka