was it a visual basic catastrophic failure? the catastrophic failure could
have been an add in the was not installed correctly. if you still have the
problematic file, try unchecking one add in at a time and exiting and
re-starting excel until you find the one that caused it.

--


Gary

"plh" wrote in message
...
I had a real scare earlier this week because of a project the I am
collaborating
on with some other people. I have Office 97 and another team member has
2002 or
something. The client has Office 97 so I am leaving mine as is. Anyway, he
sent
me a file that he says he had saved as as 97, but every time I went to
save it,
I got that warning message about lost features, no matter what if I said
yes, or
no and re-saved under another name, it just kept coming back. Then later
while I
was working in VBA I suddenly got a "catastrophic failure" which set me
back
hours. I took all the worksheets and carefully pasted them into a brand
new
workbook, and in VBA created new modules and pasted the source code in
there.
Only then did I feel confident, and lo, there have been no more
catastrophes.
But my question to all the knowledgeable people out there is: what is the
best
way to handle this situation? How can my partner get the "save as" to
truly
"save as"? I don't want to give it to the client that way, with a
disturbing
message at the end of each use.
Thank You,
-plh


--
I keep hitting "Esc" -- but I'm still here!