Declaration of variables for forms

[Rob]

I am doing something wrong in declaring variables for
forms I want to load. When the declaration is read, the
form closes. I have a form, Form1, that loads at
startup. After the Windows-generated code for Form1,
there are a few declarations: Public Shared frm2 As New
Form2, Public Shared frm3 As New Form3, etc., for five
different forms called from Form1. I've just added a new
form to the application, Form6, and declared it
as "Public Shared frm6 As New Form6" As soon as this
line of code is read, the main startup form closes,
causing the application itself to close. I've
experienced this problem elsewhere in my code, where a
form will close unexpectedly, obviously due to the way
I'm declaring the form variables. What can I do to fix
this? I have already tried declaring the variables
inside the subroutines where the forms are called up, and
I've tried declaring them in various ways, i.e., Dim
Withevents, Public Shared Withevents, etc.

[Richie Glenn]

Rob

If I understand you, you have

Class Form1
Dim Shared frm2 As New Form2
Dim Shared frm3 As New Form3
Dim Shared frm4 As New Form4
Dim Shared frm5 As New Form5
Dim Shared frm6 As New Form6

and it dies on the last one.

This is either due to there being 5 of them (unlikely) or it's due to Form6.

Replace
Dim Shared frm6 As New Form6
with
Dim Shared anotherfrm5 As New Form5
and see if it still happens.

If so, there is a problem. If not, then Form6 is doing something wrong in
its constructor (Sub New)

Richie

[Rob]

Richie

Thanks for your help. I tried declaring another variable
for a different form and it worked fine. I've examined
Form6's constructor and can't see that it looks any
different than any other form's constructor. I don't
know how anything could go wrong with the constructor
anyway, since VS does the constructing. Here is the
first part of it if you can take a look at it:

Public Class frmSPARKBar
Inherits System.Windows.Forms.Form

#Region " Windows Form Designer generated code "

Public Sub New()
MyBase.New()

'This call is required by the Windows
Form Designer.
InitializeComponent()

'Add any initialization after the
InitializeComponent() call

End Sub

'Form overrides dispose to clean up the component
list.
Protected Overloads Overrides Sub Dispose(ByVal
disposing As Boolean)
If disposing Then
If Not (components Is Nothing)
Then
components.Dispose()
End If
End If
MyBase.Dispose(disposing)
End Sub

[Fergus Cooney]

Hi Don,

There's nothing obviously wrong. Does frmSPARKBar use DC or AC?

Seriously though, I guess there are some more things tio try.

One is to see if having New Form6 as the <first> makes it die. That can
indicate or eliminate a cumulative effect. And that makes me think of a
question - how do you know that it dies then? If it's because there's an error
message....?

Another test: If it's definitely dying in New Form6 then it has to be
something in InitializeComponent. If you avoid changing the Form when in the
Designer, you can add code to InitializeComponent without it being wiped out
by the autogenerator. You can thus add loads of debugs/MsgBoxes to narrow the
gap down.

Finally, you could post some more info here. If you're totally stumped, it
might be best to post the project in a zip (without the obj or bin
directories). See if you can eliminate Forms 2 to 5 as well while still
retaining the problem.

Good luck.

Regards,
Fergus