Vb.net - how do I get the name of the form which has called another form_load

Question

0.00/5 (No votes)

See more:

I tried DirectCast(sender, Form).Name (which should say frmA) but this returns the name of the form just loaded (frmB), not the form frmA which called this Form_Load (because of frmB.Show()). Of course, there are ways around it. I can write the name of the calling Form frmA onto a label or text box on this form frmB, but I would like to learn how to use sender and EventArgs.

What I have tried:

I tried DirectCast(sender, Form).Name (which should say frmA) but this returns the name of the form just loaded (frmB), not the form frmA which called this Form_Load.

Posted 12-Sep-21 18:41pm

VBeginner.NET

Updated 12-Sep-21 20:36pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2021-09-12T19:52:00

Basically, you probably shouldn't - it's against the principles of OOPs.
If you have two forms: a Parent form which creates and displays a Child form, then OOPs says that the Child should be independent: it should have no idea that the Parent even exists, much less what type it is. Indeed, once the Child has been created, the Parent could even be Closed and Disposed and it should have no affect on eth application (unless it it the main application form, in which case the app closes as well)

Instead, the child should communicate back to the Parent via Properties and Events, just like Controls on your Forms do at the moment.
Have a look here:
Transferring information between two forms, Part 1: Parent to Child[^]
Transferring information between two forms, Part 2: Child to Parent[^]
Transferring information between two forms, Part 3: Child to Child[^]
They show teh various ways to do it - teh code is in C# but it';s pretty easy to follow and online converters can help if you don't understand the syntax: Code Converter C# to VB and VB to C# – Telerik[^]

But if there is a really, really good reason why you need to get information on a form's creator, it is available in the Load event hander via the sender parameter, which holds the instance of the Parent Form:

VB

Private Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load
    Console.WriteLine(sender.GetType())
End Sub

Will show you the class type.

But just because you can do something, that doesn't mean you should: if you think that that will help you, you are probably just making life harder for yourself in the future - a lot harder!