3 Replies Latest reply: Sep 7, 2011 8:09 AM by RodWard RSS

    Captivate 5.5 Projects on Captivate 5

    VEE2KAEY Community Member
    VEE2KAEY Sep 7, 2011 6:52 AM

      Hello,

       

      I have just intalled Captivate 5.5 on my PC. I shared this information with my other team members and I came to know that there is a serious issue. All my other team members have Captivate 5 and I was informed that if I make any changes to an existing project in v5.5, it won't be accessible in v5.

       

      I just Googled some things and came to know that many users have this issue while working on a shared project.

       

      Is this really true? If yes, then what is the solution?

       

      Thank You,

      VEE2KAEY

      • 1389 Views
      • Tags:
        • 1. Re: Captivate 5.5 Projects on Captivate 5
          RodWard CommunityMVP
          RodWard Sep 7, 2011 7:00 AM (in response to VEE2KAEY)

          You're not going to like this but...there is no way to save files from Cp 5.5 down to Cp 5.

           

          So your only options are for everyone else to upgrade to Cp 5.5 or else you'll have to downgrade again to Cp 5.

           

          New versions of Captivate have never been backward compatible.  It's caused a lot of people grief over the years and is one reason why some of us have several versions of Captivate still installed on the same PC.

          • 2. Re: Captivate 5.5 Projects on Captivate 5
            VEE2KAEY Community Member
            VEE2KAEY Sep 7, 2011 8:01 AM (in response to RodWard)

            Thank you for the information Rod. But isn't there anything or any patch that can make things work? I know this is an issue from Adobe's side. I am also searching for the same.

             

            I have purchased Captivate 5 in January and v5.5 now. If this was known, I could have searched for 5. An upgrade will make me spend more.

            • 3. Re: Captivate 5.5 Projects on Captivate 5
              RodWard CommunityMVP
              RodWard Sep 7, 2011 8:09 AM (in response to VEE2KAEY)

              Sorry, but I can't give you any good news on this front.  Lots of other people have complained about this same issue for several versions now.  I know of no solution.