Re: Ghostly presence of Excel process

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Roy,

Inasmuch as Excel DOES stop running at the end of the StripXLFormats
procedure, I will abandon my attempts to understand why it loops endlessly
before the function ends (for now).

However, now that I have everything running just fine, Shell function and all,
I hate it!

One of the sheets that is getting formatted for a currency type ("$#,##0.
0###") consists of a matrix having in the neighborhood of 170X170 cells. This
is taking forever. Although I've gained a lot of knowledge perfecting these
procedures, I don't know that my users will sit still for a formatting
process that may take several minutes.

In your opinion, would it be respectable to export at least this one
work*** as a text file, convert it to CSV, open it in Excel, save it as an
Excel workbook/work***, and finally Move the thing over to the workbook?

Thanks,

Bill

RoyVidar wrote:
ragtopcaddy via AccessMonster.com wrote in message <5e07eb4a8c7d6@uwe>

Many thanks (yet again!) to you and Roy,

[quoted text clipped - 57 lines]
formatted, [quoted text clipped - 124 lines] Err.Clear
End Function

My view is to focus on *not* getting an extra instance of excel in the
first place - i e work with the cause of it - not trying to get rid of
it afterwards, which is more like dealing with the symptoms. The link I
gave, should give some hints on that.

For me to be of further assistance, I think I'd like to see the current
code. See also if it makes any difference instantiating with
createobject in stead of with the New keyword, and leave off all that
IsExcelRunning stuff. For instance something along the lines of the
following air code:

on error resume next
Set xlObj = GetObject(, "Excel.Application")
if err.number <> 0 then
' ouch - no instance open, then create one
err.clear
Set xlObj = createobject("Excel.Application")
if err.number <> 0 then
' double-ouch - is excel installed???
exit sub
end if
end if
on error goto <your error handler>

You might perhaps drop in a DoEvents after saving/closing the workbook,
and also after quiting excel?


--
Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Message posted via http://www.accessmonster.com
.

Quantcast