By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,825 Members | 1,103 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,825 IT Pros & Developers. It's quick & easy.

Lock up on Inheriting from an existing form

P: n/a
foo
Hello,

I have a form that I developed in a small simple project. The form runs
fine by itself. When I try to create a new form that inherits from this
form, the machine goes off in the weeds for many minutes and throws off an
error 5 "Invalid procedure call or argument", and uses up all the machine
resources so Windows has to increase them in order to continue. It never
does finish the operation of creating the new form. I have to kill and
restart VB .Net and manually add this new form to the project, where the
same thing happens all over again.

What's really strange is that during this inheritance process the .Net IDE
somehow gets into my error logging code and tries to write error messages to
my error table in an Access db. It's as if it started to execute the new
form and somehow ended up in the error handling logic.

I'm perplexed.

Bill Nicholson
Cincinnati, OH USA
Nov 20 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
* "foo" <fo*@foo.com> scripsit:
I have a form that I developed in a small simple project. The form runs
fine by itself. When I try to create a new form that inherits from this
form, the machine goes off in the weeds for many minutes and throws off an
error 5 "Invalid procedure call or argument", and uses up all the machine
resources so Windows has to increase them in order to continue. It never
does finish the operation of creating the new form. I have to kill and
restart VB .Net and manually add this new form to the project, where the
same thing happens all over again.

What's really strange is that during this inheritance process the .Net IDE
somehow gets into my error logging code and tries to write error messages to
my error table in an Access db. It's as if it started to execute the new
form and somehow ended up in the error handling logic.


Add this around the code:

\\\
If Not Me.DesignMode Then

' Updata database here...
End If
///

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>
Nov 20 '05 #2

P: n/a
foo
I don't know where to add this code because the inheritance process is being
performed from the IDE. I'm not trying to inherit programatically. I right
click the project in the project explorer, select Add, etc...
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bu************@ID-208219.news.uni-berlin.de...
* "foo" <fo*@foo.com> scripsit:
I have a form that I developed in a small simple project. The form runs
fine by itself. When I try to create a new form that inherits from this
form, the machine goes off in the weeds for many minutes and throws off an error 5 "Invalid procedure call or argument", and uses up all the machine resources so Windows has to increase them in order to continue. It never
does finish the operation of creating the new form. I have to kill and
restart VB .Net and manually add this new form to the project, where the same thing happens all over again.

What's really strange is that during this inheritance process the .Net IDE somehow gets into my error logging code and tries to write error messages to my error table in an Access db. It's as if it started to execute the new
form and somehow ended up in the error handling logic.


Add this around the code:

\\\
If Not Me.DesignMode Then

' Updata database here...
End If
///

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

Nov 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.