Tom,

Advice well taken! I'll be more careful in the future!

Thanks for your patience and insight.

You have continued to help me too much for me to jeopardize that...

--
sb
"Tom Ogilvy" wrote in message
...
Your just talking about a lot of work and possibly her job if she claims
she
introduced a virus into her companies network. You gave the correct
advice
to experiment with a clean workbook and see if there is a problem. I
would
just go slow about suggesting more aggressive solutions for a problem that
sounds much more like user error until these had been ruled out. Since
the
changes could be done in a single command and the workbook saved - that
would be easy to test and the previous cause could be ignored unless the
problem was recurrent.

--
Regards,
Tom Ogilvy

"steve" wrote in message
...
Tom,

Never knew (or noticed) the Saved Property in the properties window. I
was looking in all the wrong places. Did know about the code version
(thanks to the forum).

I may have been on a 'fishing trip' and am now not sure if it was the
right
thing to do. But I was hit by the 'worn' recently and it raised havoc
with
my
Excel. Had to have my machine debugged by the IT group and Excel
reloaded.

Sorry if I over reached...
--
sb
"Tom Ogilvy" wrote in message
...
Go into the project explorer window in the VBE and select the
thisworkbook
entry in the tree under your workbook. Look in the properties window
(F4
if
it isn't visible) and you can see the Saved property.

Really Steve, you should tell Carol you are on a fishing trip here.
Suggesting she may need to reload excel is kind of outlandish.

As for the worm, do you have some knowledge of what the word does - is
it
a
known fact that it affects excel?

--
Regards,
Tom Ogilvy


"steve" wrote in message
...
Carol,

I am unaware of how you viewed the Saved Properties. Could you
explain
it to me? (Please!)

Suggest you play with your test workbook. Enter some formulas, save
and
close the book. Reopen, edit some formulas, save and close. And
see
if
it is working for you.

If the above works - than your original book may have become
corrupted
in some way. You'll have to rebuild it. But that won't be too
terrible -
just
open a new book and copy and paste each sheet from the old to the
new.
Than save it and test it.

If the problem persists - your Excel may have become corrupted and
you'll
have to reload it.

Or worse - you got that nasty worm that has been floating around in
a
pseudo MS email. In which case you'll have to get your IT people to
disinfect your machine and than reload Excel.

Hope that it's the easier of the alternatives. Reply back (using
reply
will
insure that I spot your post faster).

And I'll try to stay with this until you're out of the woods and
safely
to
GrandMa's...

--
sb
"Carol" wrote in message
...
Sending this as a NEW mail, due to Runtime errors received on
"Reply"
emails...ugh.

Oh Steve.

Your VBA comment has me worried: I found a code in this newsgroup
the
other day that I thought would automatically hide the blank lines in
my
workbook. Problem is, I know nothing about VBA - except how to
display
it.
That didn't stop me though - I went into VBA and added the code I
found
to
my worksheet. I then saved the book as TEST, and forgot about it as
I
didn't know how to run the code to see if it worked.

The workbook I'm having the formula problem in is different than
the
test,
and I've gone into each worksheet in VBA and verified there is no
coding
showing. Although, when I open the properties for "this workbook"
(in
VBA), there is a line that says "Saved" and the next column reads
"false"...
I have no idea what that means.

I just checked the TEST book, and the coding I did the other day,
is
not
there....which only proves I had no idea what I was doing... but if
that's
the case, then VBA is not the problem...right? Though - the
properties
for
this workbook on the Saved line show True.

I'm sorry to spew so much information - yours is the only response
the
hit
the closest to home. I know I wasn't working on a "temp" copy,
because
my
non-formula changes were saved! And I wasn't working on a network
copy
either....

SO. If you don't think it's VBA, I'll just make a few fixes, save
them,
test them, and go from there!

Thank you!
Carol