| Home |
| Search |
| Today's Posts |
|
|
|
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
[GetMacroRegId] in Immediate window
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 |
|
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
I noticed something similar when I switched to Excel 2003. I had a
momentary fear that a virus had somehow infiltrated Excel, but I was able to track it down to an Excel 4 macro that the Solver add-in was using to run some initialization/registration code. I don't know what changed between Excel 2000 and 2003 for this change in behavior in old add-ins. I just highlight and delete - annoying maybe but over in a second. On Feb 2, 6:22 pm, "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 |
|
#3
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
Not that it really matters, but I realized that it probably isn't the
Exel 4 Macro displaying solver's junk (which doessn't seem as bad as what you are reporting). Even though I can no longer figure out how, I was able to unhide Solver's macro sheets (which are not password protected) and they had (iirc) an auto-open() which did the sort of registration being reflected in the immediate window, so I took that as an explanation of what I was seeing - but I don't think such an old- style macro sheet would have access to the immediate window. Out of curiousity, does anybody know how to render add-in Excel4 macro sheets visible? It's been over a year and I can't remember how I did it. On Feb 2, 6:44 pm, "John Coleman" wrote: I noticed something similar when I switched to Excel 2003. I had a momentary fear that a virus had somehow infiltrated Excel, but I was able to track it down to an Excel 4 macro that the Solver add-in was using to run some initialization/registration code. I don't know what changed between Excel 2000 and 2003 for this change in behavior in old add-ins. I just highlight and delete - annoying maybe but over in a second. On Feb 2, 6:22 pm, "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- Hide quoted text - - Show quoted text - |
|
#4
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
[GetMacroRegId] in Immediate window
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 |
|
#5
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
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 |
|
#6
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
On 2 Feb, 16:52, "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- Hide quoted text - - Show quoted text - This debug.print code in the anylsis toolpack causes debugging my Visual Basic code extremly difficult since it clutters up the Immediate window. Also it slows down my code. Does Microsoft have a patch? Duane |
|
#7
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
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 |
|
#8
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
On 2 Feb, 17:00, Dave Peterson wrote:
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 - As someone who make his living writing software I agree with you. Ok so I can't get the password.... so back to my original question... how do I get rid the debug.print code ( [GetMacroRegId] ) that writes to the Immediate window? thanks Duane |
|
#9
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
You'd need the password--or a way around the password.
Maybe someone will share it. I won't. bigHatNoCattle wrote: On 2 Feb, 17:00, Dave Peterson wrote: 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 - As someone who make his living writing software I agree with you. Ok so I can't get the password.... so back to my original question... how do I get rid the debug.print code ( [GetMacroRegId] ) that writes to the Immediate window? thanks Duane -- Dave Peterson |
|
#10
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
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 |
|
#11
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
I didn't say it was valuable intellectual property <vbg. I just said it
belonged to the people/company that wrote the addin. 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 -- Dave Peterson |
|
#12
Posted to microsoft.public.excel.programming
|
|||
|
|||
|
in Immediate window
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 |
| Reply |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| how to save a desired window size but hv window comeup fullsz by d | Excel Discussion (Misc queries) | |||
| View cell contents as a pop-up window (similar to comments window) | Excel Worksheet Functions | |||
| Docking Project Explorer, Properties window and Code window in VBE | Setting up and Configuration of Excel | |||
| The window opens in a smaller window not full sized window. | Excel Discussion (Misc queries) | |||
| In Excel - how to delete new window created from window on tool ba | Excel Worksheet Functions | |||
![bigHatNoCattle[_2_] is offline](https://www.excelbanter.com/images/SultanThemeVB3R/statusicon/user_offline.gif)
Hybrid Mode
