Seriously, Adobe.
You need to get your act together. Captivate has become the red-headed step child of your products.
I have a coworker that just lost ALL her work because she hit a button while saving, which apparently Captivate doesn't like. This is not something that should break a file. But now she is left with 3 weeks worth of work down the drain.
You have to understand that you are setting people up for failure by having issues like this.
And it is not an old issue. While troubleshooting for this I've found the EXACT SAME problem countless times in this forum, some dating back to 2010.
WHAT IS THE DEAL?
Ok, so before you all say "try this"... This is what we have tried:
1. Using the cache files through the adobe "AIR" package -- the cache files we were able to recover were almost 3 weeks old, when she first created the file. This is not helpful. There were no cache versions between that time and the time it crashed, contrary to what Adobe says. So where are the missing cached files???
2. Using backup files -- no backup files because this is not set by default, which we did not know.
Bottom line:
1. A person should not have to be afraid that caching/backup won't work properly.
2. A person should not have to be afraid of hitting a button while the program is saving.
3. People's jobs are at stake. Saying "this may not work" when a file randomly get's corrupted doesn't cut it. You need to fix these problems. Already, her boss is considering getting rid of Adobe products and using other software for instructional design.
So, can anyone else shed some light onto other possible solutions? We've looked all over the internet and tried the above, but feedback is welcome.
Thanks
