F
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
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