View Single Post
  #3   Report Post  
Posted to microsoft.public.excel.programming
davegb davegb is offline
external usenet poster
 
Posts: 573
Default Macro buttons causing XL fatal errors?


keepITcool wrote:
close excel.

clean your temp directory...

windows/start/run %temp%
will get you there.

1000 files?.. or more?

delete everything (files and folders)!
1 or 2 files cannot be deleted because there 'in use'
the rest should go.

now keep watching that dir when you start excel,
and open your favourite 'shape-rich' workbook..

see why I dont like embedded controls?


--
keepITcool
| www.XLsupport.com | keepITcool chello nl | amsterdam


davegb wrote :

I've been getting fatal errors in XL2000 a lot lately. I looked around
here to see if I could find some info on the problem. I found a thread
saying that "controls" can cause XL lockups. Does this mean macro
buttons? In my case, macro buttons are just buttons I create from the
"Forms" toolbar, rename and assign a macro to. Do they cause XL
lockups?
I downloaded a program called "CodeCleaner" but it didn't install,
apparently. When I tried to run it per the instructions at the end of
the install, the command to run it doesn't appear on my "Tools,
Options" menu as it's supposed to. It's there and checked in the
"Add-ins" menu, but not anywhere I can access it. Tried from both the
spreadsheet and the VBE editor.
Is this the most likely source of my problem? If so, what can I do
about it? If not, what is the most likely source and what can you
reccommend about that?
BTW, I don't think it's memory related. I have 1G of memory. I do,
however, run a lot of stuff normally, including the 2M XL file I'm
usually working on and maybe one or two others, Novell GroupWise, my
browser, and often a file folder or 2 and possibly a Word documemt. I
added it all up from the Task Manager and show just over 200M.
Thanks in advance.


Thanks for the help. I deleted everything it would let me delete. There
were about 60 items including folders. 6 it would not let me delete.

Why do embedded controls cause this problem? Is MS planning on fixing
this or is it just not common enough for them to worry about (I imagine
less than 1% of users use embedded controls)? What are the alternatives
to embedded controls for very basic end users (many of them think
adjusting column widths is advanced XL!)?