From: Robert on
Hello,

I have recently had problems with the VB6 IDE crashing for no apparent
reason. The only major change to my system is that I have installed Windows
XP Service Pack 3. I have one particular application that will simply close
the IDE and give no errors. I have another application that generates an
error that VB6 unexpectedly caused and error and will be closed. Neither of
these instances generate an event log. I do not have Windows Firewall turned
on and I have Visual Studio Service Pack 6 installed.

Has anyone else had any problems?

Thanks,
From: dpb on
Robert wrote:
....
> I have recently had problems with the VB6 IDE crashing for no apparent
> reason. The only major change to my system is that I have installed Windows
> XP Service Pack 3. ...
> ... I do not have Windows Firewall turned
> on and I have Visual Studio Service Pack 6 installed.
>
> Has anyone else had any problems?

Can't say, I'm at SP2.

Two suggestions...

First, get latest of whatever anti-virus package you use and run it and
see it finds anything fixable then try VB again for a while.

If not, try the rollback of SP3.

--
From: MikeD on

"Robert" <Robert(a)discussions.microsoft.com> wrote in message
news:24534A8B-C24B-44C9-B59A-5B7D4F4EF902(a)microsoft.com...
> Hello,
>
> I have recently had problems with the VB6 IDE crashing for no apparent
> reason. The only major change to my system is that I have installed
> Windows
> XP Service Pack 3. I have one particular application that will simply
> close
> the IDE and give no errors. I have another application that generates an
> error that VB6 unexpectedly caused and error and will be closed. Neither
> of
> these instances generate an event log. I do not have Windows Firewall
> turned
> on and I have Visual Studio Service Pack 6 installed.
>
> Has anyone else had any problems?
>

Not that this is a whole lot of help for you, but I've got 2 virtual PCs
which I've updated to WinXP SP3 (from SP2) and have had no problems with VB6
itself or apps created with VB6.

Even in order to speculate, however, we'd need to know more details about
these 2 apps. For example, do they use any features or components that SP3
updates? Does the problem only occur within the IDE or do the compiled apps
also cause these crashes? Can you install these same apps to another PC that
does NOT have SP3 installed? If so, do the apps still crash? If you don't
have Virtual PC, you might want to consider getting it because it's GREAT
for helping with these kinds of things. You can download it here:

http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx

There are also other similar programs from vendors besides MS. Virtual PC
2007 is free; however, you DO need a legitimate license for the OS and any
software you install on the VPC because for all intents and purposes, the
virtual PC *is* another computer. Windows itself is not much of an issue for
anything short-term. Simply don't activate it. Installing VB6 on multiple
VPCs isn't an issue at all (although legally I suppose you SHOULD have
licenses for VB6 for each VPC on which you install it). Other software
depends. Best to check with the software's publisher/manufacturer. For any
software that requires "activation", you could have problems and have to buy
another license to use that software on the VPC.

I find it interesting that you mentioned Windows Firewall. That's not
something that I, for one, would give much consideration to unless my app
was doing something with Windows Firewall (trying to grant itself access to
a certain port or whatever). Yet, you thought enough of it to explicitly
mention you had Windows Firewall turned off. Why?

You might have to have your app write to its own event log...including line
numbers in your app and logging each line number that executes. It might be
overkill to actually log each and every line of code...at least at first.
But sometimes, that's what you have to do to solve these kinds of issues. If
you do have to resort to that kind of logging, it should ONLY be in a
special debug version of your app. Once you've determined the issue and
corrected it (if you can), you need to remove this level of logging because
it can seriously detract from performance. For debugging purposes,
performance is not the goal. Finding and fixing the problem is the goal.

--
Mike
Microsoft MVP Visual Basic


From: .NET Sales on
"Robert" <Robert(a)discussions.microsoft.com> wrote in message <news:24534A8B-C24B-44C9-B59A-5B7D4F4EF902(a)microsoft.com>...

> Hello,
>
> I have recently had problems with the VB6 IDE crashing for no apparent
> reason. The only major change to my system is that I have installed Windows
> XP Service Pack 3. I have one particular application that will simply close
> the IDE and give no errors. I have another application that generates an
> error that VB6 unexpectedly caused and error and will be closed. Neither of
> these instances generate an event log. I do not have Windows Firewall turned
> on and I have Visual Studio Service Pack 6 installed.
>
> Has anyone else had any problems?
>
> Thanks,

This behavior is by design. The VB6 IDE is no longer supported.
Please contact Microsoft Sales for an upgrade to VB.NET.


From: Lorin on
Sounds like it is an IDE problem.
So, open the IDE.
Go to AddIn manager and uncheck all.
Try running again.
Maybe restart IDE after addins are off.
If this works, then put in addins one by one and see which one cause the
problem.

"Robert" <Robert(a)discussions.microsoft.com> wrote in message
news:24534A8B-C24B-44C9-B59A-5B7D4F4EF902(a)microsoft.com...
> Hello,
>
> I have recently had problems with the VB6 IDE crashing for no apparent
> reason. The only major change to my system is that I have installed
> Windows
> XP Service Pack 3. I have one particular application that will simply
> close
> the IDE and give no errors. I have another application that generates an
> error that VB6 unexpectedly caused and error and will be closed. Neither
> of
> these instances generate an event log. I do not have Windows Firewall
> turned
> on and I have Visual Studio Service Pack 6 installed.
>
> Has anyone else had any problems?
>
> Thanks,