Experience under Manual calculation "kingdom" and some trivia

H

Hari

Hi,

It doesnt trouble me anymore because I have adjusted my work settings but
just wanted to share what I faced in the past.

If our calculation is set to manual then "text to columns" feature takes a
lot of time (and may even hang).

Also, in manual calculation setting if I run a macro which queries the no of
files in a folder ( and subsequently do some operation of those files) using
"With Application.FileSearch" then it works from past memory. That is if I
have 10 files and run the filesearch it will show as 10 files. Now, if i go
and add / delete some files the and change the calculation to manual then
With Application.FileSearch will still show as 10 ( and in case of delete
the code may crash as it will be trying to open a already deleted file.)

Also, in NG's I came across some people like Frank K. using the following
word's :-

1. sub foo() - What does foo mean. Is it some sort of very common
phrase/word in programming?
2. OP - What does OP stand for?

Regards,
Hari
India
 
D

Dave Peterson

Foo is a generic placeholder--I think it was primarily used by UNIX jocks. But
it's creeped into windows jargon, too.

http://en.wikipedia.org/wiki/Foo

OP = Original Poster (the person who started the thread).

===
I've never noticed any difference with text to columns with calculation manual
or automatic. But I usually have calculation set for automatic.

And I couldn't reproduce your findings with .filesearch.

But if you're using xl2002, you may have been hit by .filesearch's flakiness.
Sometimes it returns the wrong number of files--even returning 0 when there are
files!
 
H

Hari

Hi Dave,

Thanx a lot for pointing me to wikipedia. Its very good.

Im using excel 2002, may be thats why I was facing this problem. ( Actually
I have a very heavy file which takes a lot of time in calculations so
whenever I work on that file i have turn the calculation to manual. I
noticed that when this file was open and Im running some other macros which
had text to columns and filesearch they use to sort of get abnormal. But, If
i dont have my heavy file open and turn the calculation to automatic then my
original macros were fine.To establish that the problem was due to excel
manual calculation only and not due to the heavy file , I once ran the macro
with heavy file closed and excel's manual calculation enabled and the macro
still behaved abnormally. So, I guessed that it was the manual calculation
which was causing the problems).

Regards,
Hari
India
 
D

Dave Peterson

Excel is a large beast. Sometimes it can look like something is causing
trouble, but it's just a coincidence.

Other times, it can look like something is causing trouble and that's because it
is.
 
Top