I've decided I don't really want to delete the macro after it runs; what if
the user wants to add another entry after they've already saved the
workbook? The macro is supposed to double check their input, and if it
self-deletes that won't be possible. This leads me to another question I'll
post in another topic in a few minutes.

"Tom Ogilvy" wrote in message
...
That's why you will need to use Chips page to write code to go in and
delete
you procedure.

Eventually you will need to save the workbook to "seal" your deletion, but
you can't do it in the same sub. The code isn't deleted until it
completes.

--
Regards,
Tom Ogilvy


Bill Oertell wrote in message
...
I'm having problems with my Outlook Express, so I'm forced to keep my
posts
much shorter than I'd like. But I didn't mention that the Sub I want to
delete has to run as Private in ThisWorkbook.