Hi

Here is an idea (less than ideal but maybe better than nothing) -
create your own window for displaying status messages.

As an experiment I created a modeless userform (ShowModal set to
False) named frmStatus (and captioned "Status Window" but so what)
that contained nothing but a text box named tbStatus with multiline
set to true (I don't know if that was really needed) and Scrollbars
set to option 3. Then in a general code module I wrote:

Sub PrintStatus(msg As Variant)
frmStatus.tbStatus.Text = _
frmStatus.tbStatus.Text & msg & vbCrLf
DoEvents
End Sub

It is used like this (note the need to show the form explicitly in any
sub that wants to use it):

Sub test()
Dim i
frmStatus.Show
For i = 1 To 10000000
If i Mod 10000 = 0 Then
PrintStatus i
End If
Next i
End Sub

I agree that it is a shame that the Analysis tool pack trashes the
intermediate window so much, but hopefully the above could be of some
use.

-John Coleman



On Feb 10, 11:24 am, "bigHatNoCattle" wrote:
Hi,

My app uses functions in the Analysis tool pack. I switched to Excel
2003 and now the Immediate window has the following junk. Does Excel
2007 have the same problem with this junk?

Below is the junk.

[auto_open] <
[SetupFunctionIDs] <
[SetupFunctionIDs]
[PickPlatform] <
[PickPlatform]
[VerifyOpen] <
[VerifyOpen] 1
[RegisterFunctionIDs] <
[RegisterFunctionIDs]
[auto_open]
[GetMacroRegId] 'DEC2HEX' <
[GetMacroRegId] 'DEC2HEX' - '1555300407'
[GetMacroRegId] 'DEC2HEX' <
[GetMacroRegId] 'DEC2HEX' - '-917438410'
etc etc... about 10,000 times

Considering my app calls DEC2HEX about 10,000 times this makes the
Immediate window useless for displaying status messages from my VBA
program.

I know I can erase this stuff but I'm trying to get a solution so it's
not displayed in the first place.

Duane