If there's a Win 10 compatibility setting for earlier releases, you might
want to try that. Perhaps also reinstall FM 8 in that earlier-release
environment. Just a thought.
HTH
On Wed, Oct 4, 2017 at 5:40 PM, Lea Rush wrote:
> Hi all,
>
> I've been running Frame 8 since the days when we rubbe
Thanks for the warning, Gayle. I don't use Freeze Pagination, so I think I'm
good to go. It's good to get feedback from someone doing exactly what I hope to
do!
Take care,
Lea
Lea Rush
Senior Software and Documentation Specialist
Astoria-Pacific
www.astoria-pacific.com
P: 800-536-3111, +1-503
Excellent. Thanks much. I'm aware of the change to the UI. That would be a
major part of the reason I've clung to Frame 8 as long as I have. Well, that
and the wild unreliability of Frame for several versions after 8. I think I've
stuck to my guns as long as I can, though.
Lea
-Original
The answer is yes. We are just doing the same thing here and there have been no
problems (5,000+ files). Sorry, one issue. Legacy feature freeze pagination
does not behave the same in Frame 2017, so we've removed it from our Frame 8
docs and converted the docs after that.
-Original Message-
You should be able to open and save them to the new format with now problem.
Nothing should have changed.
You will notice substantial changes in the interface. I suggest you walk though
the interface related videos on the Adobe site to reduce confusion.
Craig
Hi all,
I've been running Frame 8 since the days when we rubbed two sticks together to
turn on the computer. I currently have it installed on Win10 64-bit, and it's
run flawlessly until today.
Today, it crashed spectacularly. Not only did it crash, but it destroyed the
entire file. There wasn'
