thousands of lines

That is nothing! I have an .xla with some 150.000 lines.
I am happy to have a look if you send the file to me.
I can assure you I won't pass it on to anybody.

RBS


"Tom Med" wrote in message
oups.com...
The only problem with that is there are thousands of lines of VBA and
I am not sure my company would like me publishing it all. Due to the
nature of the problem there is no way I can locate which module /
class has the problem or produce a summary... Unless someone knows how
to get more information from a VBE core / stack trace

Tom

On 27 Sep, 12:48, "RB Smissaert"
wrote:
I don't think the language is bad at all, but somebody (not sure it was
you)
has made a mess and that will need cleaning up.
Maybe you could narrow it down by commenting out the Option Explicit
one by one and compiling.
Another option is to post the file somewhere and maybe someone will have
a crack at it.

RBS

"Tom Med" wrote in message

ups.com...

Well I have fixed all the errors I can find, but now when I hit the
compile button excel crashes. What is causing the crash now heaven
only knows. As there are thousands of lines of code it is hard to
know where to start from.

The new code that I have introduced has been more OO based that was
used before. But as in VBA theres is no way to control the deletion
of object my hands are tied as to "fixing errors"; it is the internals
of VBA that are causing these core dumps. Most languages you would
get some idea as to where your error was. But it seems the only way I
can debug this is by removal of chunks of code at a time and narrowing
it down this way.

This trial, error and coredump method of debugging is probably the
slowest development method I have come across, is there really no more
effective way to debug VB code, or is the language really that bad?

On 27 Sep, 12:05, "RB Smissaert"
wrote:
OK, there is your problem then.
You have some poor code with lots of errors and you will have to fix
them
all.

Make sure you always have Option Explicit by doing in the VBE:
Tools, Options, Editor, tick Require Variable Declaration.

RBS

"Tom Med" wrote in message

roups.com...

I have been trying to work this out, however after changing my
classes/
module to have option explicit at the top has been problematic. As
VBA now cores when I hit the compile button as I am trying to find
all
the errors.

I think this is something to with VBA mis-managing objects and
trying
to reference deleted objects, but it seems nigh on impossible to
detect what the root cause of this is.

Thanks
Tom

On 27 Sep, 10:03, "RB Smissaert"
wrote:
Does the code compile when you have Option Explicit
at the top of every module, form and class?

RBS

"Tom Med" wrote in message

groups.com...

I have tried this, or I am using an adapted version of this that
imports and export all the code on opening and closing of a
workbook.
I think it is something to do with the destruction of the objects
that
I am creating in the VBA. Both the close of the workbook and the
stop
method seem to cause these problems

Thanks
Tom

On 26 Sep, 21:02, "RB Smissaert"
wrote:
Download and run the VBA Code
Cleaner:http://www.appspro.com/Utilities/CodeCleaner.htm

Quite likely it will fix the problem.

RBS

"Tom Med" wrote in message

groups.com...

VBA is just about driving me mad... it seems every week now I
come
across something new that will cause it to crash. This time
it
is
when I hit the stop/reset button on the VBA IDE. I have no
idea
what
is causing it or where to start looking even. Has anyone else
come
across this problem, and what might be causing it and how to
fix
it?

Does anyone know how you can detect why VBA crashes? I seem to
have
it
crashing if you try and do anything other than simple
formatting
of
cells. This trial and error then crash and restart style of
programming is the most mind numbing thing in the world.

Is there anyway to debug into the VBA6 dll to find out what
the
root
of these problems are? I am hitting about 20+ crashes a day
at
the
moment, and it is driving me mad

Thanks
Tom