Re: VB6 crashes after writing exe

I have had the similar experience. I do not know however the exact reason
why this phenomenon apppears. In my case it always went away after some
time. I assume this is due to code that runs OK in the IDE but causes the
VB.exe to crash after compiling and writing the exe.

Code that for some reason has a flaw that the compiler can not digest. The
best example I know of is using the END statement in a UNLOAD event,
assigning improper values to a variable or OCX property (a SINGLE to a LONG
or an INTEGER to a LONG) or the different behaviour of events in the IDE and
the exe file (especially interdependent LOSTFOCUS and GOTFOCUS events). The
best thing to do is look careful at Your code and see where it could be
improved or optimized. Change it and see if the crashing disappears.

Furthermore it is a good pratice to have a history af backups, so You can go
back to the point where the crashing did not appear.

Yours friendly,

Hans Heezemans/Iservi
www.iservi.com


"Bruno Köller" <mydevicenull@xxxxxxxxxxxxx> schreef in bericht
news:d8v0m4$tcd$1@xxxxxxxxxxxx
>I have a VB6 application carefully tested in the IDE and often compiled
>while expanding the source code step by step. Now VB crashes after
>compiling and writing the exe file.
>
> I know, of course, that nobody can tell me why. But maybe someone could
> give me a hint what could be the reason for it?
>
> It might not be a simple code error: I have tested over and over during
> code expanding, and the crash happens at compile and not at run time. I'm
> using Options Explicit, no subclassing, only some carefully checked and
> often tested API calls.
>
> Thnaks for each idea.
>


.

Relevant Pages

  • Re: Forth input line buffered, why?
    ... whether interpreting or compiling waits for the user to type ... The main reason is that it's often desirable to manage the input stream while you're in it. ... I have seen implementations that compile a command line before executing it, in order to be able to use things like IF and DO in the command line, but I think executing before the user is finished typing would be very hard to get used to. ...
    (comp.lang.forth)
  • Re: 21st Century repeat of ~ Sodom & Gomorrah ~
    ... things that I *don't* think are sinful but, in fact, are. ... No, I am asking that there should be an equal recognition, on both sides of this matter, that one might be wrong and that those on the other side have also come to a reasoned and careful conclusion. ... The whole point about the Derby Resolutions is that, across the church, we all recognise exactly what you ask me to recognise, and that we then honour the views of the others even where we cannot agree with them. ... I would not normally put you into such a category but the way you put things in this case gave me reason to wonder. ...
    (uk.religion.christian)
  • Re: OpenBSD seems Much Faster Than FreeBSD -- Why?
    ... Not that I've got any particular reason to doubt your impressions, ... you've offered exactly zero support for claims of one being faster than ... but most operating-system code benefits from staying ... What I'm getting at, is that compiling from source is, these days, ...
    (comp.unix.bsd.freebsd.misc)
  • How to make an exe file developed with pirated vb to a genuine one
    ... I will register my company and things like that and pay the taxes to ... Is there any way to overloop this and make my project an original one. ... compiling it into a exe file give it to someone who has original vb and ...
    (comp.lang.basic.visual.misc)
  • Re: Program Fails When Parameter Fixed Constants are Changed (F77) ??
    ... routine that aren't able to be resolved by the linker. ... for this _MIGHT_ be you're not compiling the module which now contains ... A reason for that could be as simple as you ... cause a link error. ...
    (comp.lang.fortran)