I thought I had this solved. By exporting all the modules to text files and
then deleting them all and then re-importing them all, as recommended by
Microsoft, all was well on Friday.

Today, Monday, not only is that solution no longer working, but I now have
three machines which spontaneously break in the middle of code.

Not always in the same place, and continue to break regardless of what I try.

I have done a complete virus and spyware scan, without any noticeable effect.

Surely someone must have an idea what has gone wrong in the past two weeks?

On some machines the spreadsheet is read form a network, on others it is
local.

What has happened in the past two weeks to stop Excel 2002 VBA code runiing
properly?

Any thoughts?????


"Jean-Yves" wrote:

If you are running on a networl, did you ever ask what other services/spy/
antivirus are running oin the background, make all
our pc running slower and slower over the months ?
Regards
JY

"DavidAtCaspian" wrote in message
...
I have a number of spreadsheets with code.

This week two of them on different PCs have begun spontaneosuly breaking
during execution, with a message

"Code execution has been halted".

With options to debug, end or continue.

They generally break in the same place, and I cannot find a way to make
them
run properly. (One one a 'paste special' line, the other on a 'wend')

They used to run OK , and still do on other machines. (The sheet has been
copied from a common location on to local machines.)

I have tried removing all break points (even though there aren't any in
there)
I have added a break at the rogue position and then removed it again.
I have put in an extra line of code, compiled, taken the line out and
compiled again, but still the VBA routine breaks.

On the 'rogue' machine I have copied the sheet down again and STILL get
the
problem.
Excel version is 2002 at SP3, OPerating system is XP at SP2 - plus I
beleive
all the latest critical patches.

Anyone else had this, or any suggestion on how to fix? -- It has only
happened so far with Excel VBA -- All the Access one are still running
'break
free'.

Thanks

David