Skip to main content
R
robertr19866040
Participant
November 6, 2024
Answered

Captivate Classic and Corrupted Files

  • November 6, 2024
  • 1 reply
  • 451 views

Our company has "old" 2019 Captivate for use with a third-party vendor's files that we need to edit (most of them are done in that version of Captivate).

Occasionally, I'll get the, "Adobe Captivate could no open . . ." prompt for projects. 

Does anyone know if Captivate Classic does a better job at opening these problematic files?

 

 

    This topic has been closed for replies.
    Correct answer RodWard

    That particular error message is often shown when a newer version of Captivate 2019 was used when the project file was last edited.  I would recommend that you DO test out using Captivate 2019 Classic on a copy of the project files that you currently cannot open. 

     

    My guess is that your vendor company might have updated their version of Captivate beyond your version.  For example, there was a significant difference between Captivate 2019 version 11.5 and 11.8.  The result was that if a file was edited with 11.8 then users on 11.5 version builds could not open and edit that file. 

    1 reply

    RodWard
    Community Expert
    RodWardCommunity ExpertCorrect answer
    Community Expert
    November 7, 2024

    That particular error message is often shown when a newer version of Captivate 2019 was used when the project file was last edited.  I would recommend that you DO test out using Captivate 2019 Classic on a copy of the project files that you currently cannot open. 

     

    My guess is that your vendor company might have updated their version of Captivate beyond your version.  For example, there was a significant difference between Captivate 2019 version 11.5 and 11.8.  The result was that if a file was edited with 11.8 then users on 11.5 version builds could not open and edit that file. 

    R
    robertr19866040Author
    Participant
    November 8, 2024

    Thanks for the feedback, Rod!

     

    Outside of the third-party vendor, our LMS Administrator is the only other person who occasionally opens the files. I've supected that there might be something with her version of Captivate that's different, and thus causing the version issue as you mentioned. That would explain problems with some of the files, but not all of them. 

     

    Some of them I had last opened, edited, and published for use. When I came back to them for updates, that message would appear (despite not changing Captivate versions and being the last person to use the file). It's been strange and frustrating, to say the least. At least the LMS Administrator has been able to open files that are now seemingly locked to me.

     

    All of that said, I *did* find the download link to the trial copy of Captivate Classic. With that installed, I was able to successfully open, edit, save, and reopen a file that was "corrupted" last month. So it does seem that the Classic client is able to help overcome this issue, for anyone else that may be experiencing it.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices