On 2 Feb, 20:14, Christmas May
wrote:
Chip,

Please email me directly, I have questions regarding our last conversation.

Thanks in advance,

Christmas May



"Chip Pearson" wrote:
The password for protected addins (either solver or the analysis toolpak)
is
there because the owner didn't want its intellectual property shared.

Actually, there is nothing to see in these add-ins. All they do is call
registered functions in a DLL. If you were to open up the XLA add-ins, all
you'd see is calls to the DLLs that do the real work, and of course the
Debug.Print statements that started this discussion. You wouldn't see any
code that does the calculations.

--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com
(email address is on the web site)

"Dave Peterson" wrote in message
...
The password for protected addins (either solver or the analysis toolpak)
is
there because the owner didn't want its intellectual property shared.

I think it's a good idea to respect that.

bigHatNoCattle wrote:

On 2 Feb, 15:59, Dave Peterson wrote:
IIRC, this junk is left over from a "debug.print" in the analysis
toolpak.

You'd have to know the password to clean it up.

(or just ignore it???)

bigHatNoCattle wrote:

Help please,

I just switched from Office 2000 to 2003. Here's an example of what
I'm getting in the Immediate window.

[GetMacroRegId] 'fnWeekNum' <
[GetMacroRegId] 'fnWeekNum' - '216727643'

How do I get rid of this junk?

thanks

Duane

--

Dave Peterson

How do I get the password and specifically what steps do I take to
delete the debug code?

Duane

--

Dave Peterson- Hide quoted text -

- Show quoted text -

All the answers so far have yet to really solve my original question.
Here's my quesiton again.

How do I get the following junk from being written to the Immediate
window?

[GetMacroRegId] 'fnWeekNum' <
[GetMacroRegId] 'fnWeekNum' - '216727643'


Duane