Virus in my Immediate window?

[Mike H]

When I open my immediate window it already has some commands in, which I
don't recognise. It contains the following text:

[auto_open] <

[SetupFunctionIDs] <

[SetupFunctionIDs] >

[PickPlatform] <

[PickPlatform] >

[VerifyOpen] <

[VerifyOpen] > 1

[RegisterFunctionIDs] <

[RegisterFunctionIDs] >

[auto_open] >


Does this mean that it's running something that I'm not aware of?

 

[Frank Kabel]

Hi Mike
yu have probably some Add-ins installed which do some Debug.Print
statements during start-up / initialization

Frank

 

[Norman Harker]

Hi Mark!

I'm afraid that this looks like a bug in Analysis ToolPak where they
have left the debug statements in. It's a bug that is in both Excel
2002 and 2003.

I've reported it and hopefully Microsoft will sort it out in the next
Service Release.

Email privately and I may be able to help.

--
Regards
Norman Harker MVP (Excel)
Sydney, Australia
(e-mail address removed)
Excel and Word Function Lists (Classifications, Syntax and Arguments)
available free to good homes.

 

[Hank Scorpio]

Hi Mike
yu have probably some Add-ins installed which do some Debug.Print
statements during start-up / initialization

Specifically, the Analysis Toolpak VBA add-in will cause this
behaviour.

When I open my immediate window it already has some commands in,
which I don't recognise. It contains the following text:

[auto_open] <
[SetupFunctionIDs] <
[SetupFunctionIDs] >
[PickPlatform] <
[PickPlatform] >
[VerifyOpen] <
[VerifyOpen] > 1
[RegisterFunctionIDs] <
[RegisterFunctionIDs] >
[auto_open] >
Does this mean that it's running something that I'm not aware of?

 

[Hank Scorpio]

Hi Mark!

I'm afraid that this looks like a bug in Analysis ToolPak where they
have left the debug statements in. It's a bug that is in both Excel
2002 and 2003.

I've reported it and hopefully Microsoft will sort it out in the next
Service Release.

Email privately and I may be able to help.

Just to clarify on that, Norman, I think you'll find that it's the
Analysis Toolpak - VBA (that is, Atpvbaen.xls(ATPVBAEN.XLA)) which
does this. If you load the Analysis Toolpak (that is, funcres
(FUNCRES.XLA)) by itself, you won't get the behaviour.

It's more a minor irritation than a real problem, but a fix wouldn't
go astray.