It was also confusing that you stated " So I have renamed Form_Load event "Activate" "
There is no such thing as "re-naming" an EVENT. An event is an event is an event. You can't rename them, only Microsoft can.
Also as Maj said naming a procedure the same as a naturally occurring event is a really bad idea and I'm not sure if it could actually cause some problems, especially if you manually changed a true Event stub to Public. Maybe not, I just avoid naming conflicts so I am not sure.
You don't "pass a property" to a form. You "pass" arguments and parameters into procedures and functions. So your post was extremely confusing.
In the very rare-if-ever case where you have written code in an Event, but due to poor planning, it's not firing because it's not really in the right event, you may be able to force the event to fire by calling it explicitly. If you're outside the class scope of that event you may need to manually change the Private event to Public. In your case it looks like you were trying to make Load fire by Activating the form, which doesn't make a whole lot of sense.
I would recommend using the right events rather than trying to fudge it.
If you take the time to explain yourself in complete detail when first creating a post, it shows responsibility and reasonableness to forum you are asking to help you, rather than putting a 10-word question that numerous people then require a lot of questions to "drag" it out.