+ Reply to Thread
Results 1 to 5 of 5

How to later and earlier versions of Excel to play nicely?

  1. #1
    plh
    Guest

    How to later and earlier versions of Excel to play nicely?

    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!

  2. #2
    Gary Keramidas
    Guest

    Re: How to later and earlier versions of Excel to play nicely?

    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" <[email protected]> wrote in message
    news:[email protected]...
    >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!



  3. #3
    Gary Keramidas
    Guest

    attachment Re: How to later and earlier versions of Excel to play nicely?

    was it similar to this?

    --


    Gary

    "plh" <[email protected]> wrote in message
    news:[email protected]...
    >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!



  4. #4
    plh
    Guest

    Re: attachment Re: How to later and earlier versions of Excel to play nicely?

    Could you please send that in a different format? MIE and Firefox both say they
    can't read it.
    -plh

    In article <[email protected]>, Gary Keramidas
    says...
    >
    >This is a multi-part message in MIME format.
    >
    >------=_NextPart_000_003E_01C66716.0DF02060
    >Content-Type: text/plain;
    > format=flowed;
    > charset="Windows-1252";
    > reply-type=original
    >Content-Transfer-Encoding: 7bit
    >
    >was it similar to this?
    >
    >--
    >
    >
    >Gary
    >
    >"plh" <[email protected]> wrote in message
    >news:[email protected]...
    >>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!

    >
    >------=_NextPart_000_003E_01C66716.0DF02060
    >Content-Type: message/rfc822;
    > name="Capture4.MHT"
    >Content-Transfer-Encoding: 7bit
    >Content-Disposition: attachment;
    > filename="Capture4.MHT"
    >



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

  5. #5
    Gary Keramidas
    Guest

    Re: attachment Re: How to later and earlier versions of Excel to play nicely?

    if you give me an email address, i'll email it to you

    --


    Gary

    "plh" <[email protected]> wrote in message
    news:[email protected]...
    > Could you please send that in a different format? MIE and Firefox both say
    > they
    > can't read it.
    > -plh
    >
    > In article <[email protected]>, Gary
    > Keramidas
    > says...
    >>
    >>This is a multi-part message in MIME format.
    >>
    >>------=_NextPart_000_003E_01C66716.0DF02060
    >>Content-Type: text/plain;
    >> format=flowed;
    >> charset="Windows-1252";
    >> reply-type=original
    >>Content-Transfer-Encoding: 7bit
    >>
    >>was it similar to this?
    >>
    >>--
    >>
    >>
    >>Gary
    >>
    >>"plh" <[email protected]> wrote in message
    >>news:[email protected]...
    >>>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!

    >>
    >>------=_NextPart_000_003E_01C66716.0DF02060
    >>Content-Type: message/rfc822;
    >> name="Capture4.MHT"
    >>Content-Transfer-Encoding: 7bit
    >>Content-Disposition: attachment;
    >> filename="Capture4.MHT"
    >>

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



+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Search Engine Friendly URLs by vBSEO 3.6.0 RC 1