No Joy.

I seem to remember having this trouble on another spreadsheet that started
as an ascii import as this one did.
Could that have something to do with it?

I am having trouble in XP - Office 2003 box, but I just opened it on a
Win7 - Office 2007 machine and had no issues.

Any ideas? (Besides the obvious . . . Dump the XP box)


Regards,
Todd



"Chip Pearson" wrote in message
...
You probably need to force VBA to purge out its internal code storage
areas. This involves exporting all your modules to text files,
removing the module itself and then importing the text files. This
cures many problems related to VBA editing and execution. The whole
export/import operation can be reduce to a mouse click using Rob
Bovey's Code Cleaner add-in. Go to
http://www.appspro.com/Utilities/CodeCleaner.htm and download and
install it. It is a must-have add-in for serious developers.

Cordially,
Chip Pearson
Microsoft MVP 1998 - 2010
Pearson Software Consulting, LLC
www.cpearson.com
[email on web site]



On Thu, 4 Feb 2010 17:08:48 -0500, "Todd Heiks"
<Todd.Heiks_AT_NoSpam_GreatLakesWindow.com wrote:

Excel 2003
VBA Macro

Anybody run into a phanton breakpoint in Excel?
The code stops without an error. Hit continue and the code finishes w/o
error.

I have run into this in MSA and had to decompile. Is there a way to
decompile Excel?

Regards,
Todd