Execute subroutine at startup

[Philosophaie]

I am trying to execute the "Data()" subroutine at startup. This did not work:

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
Call Data()
End Sub

Is there a way to call the subroutine at the begining of debug?

[Shaggy Hiker]

What did not work about that call (though you don't ever need to use the Call word, it's a holdover that can be forgotten)? Did it not happen early enough? If that's the issue, then you can move the call earlier in the process, such as to the form constructor (which is not immediately obvious, but can be found in the .designer.vb file associated with the form).

[stanav]

Can you explain what "did not work"? That is, tell us what your expected result is and what the actual outcome you have now.

[Philosophaie]

It should have made the call when the form was loaded.

[VB6 to Vb2010]

Put a breakpoint at Call Data()
Use "Step Into" <F8> , What happens?

[Philosophaie]

I put a breakpoint at Call Data() then <F8>.

No errors just Highlighted in YELLOW:

Dim gphFormGraphics as Graphics = Me.CreateGraphics

[formlesstree4]

Keep pressing F8.

[Philosophaie]

This just highlights the line. What to do next?

[jmcilhinney]

That line of code IS being executed. That I can guarantee. What may be happening is that the method you're calling is throwing an exception. In Windows 7, exceptions thrown in the Load event handler of the startup form are swallowed without obvious notification.

You are obviously doing something wrong because you should basically NEVER be calling CreateGraphics. It's especially useless in the Load event handler because the form hasn't even been displayed yet, so anything you draw will never be seen.

Please explain what you're actually trying to achieve. Showing us the contents of the is Data method would help also.

Finally, "Data" is a very poor name for a method. Method names should be verb-based for a start, because they represent behaviour. Something like "GetData" would be more appropriate, but you might be able to come up with a better name still because you know what the method actually does.

[VB6 to Vb2010]

Can you "Cut and Paste" us some of your code so we can get an idea of what you are doing?