What does "stack was produced by a newer version" mean?
J. Landman Gay
jacque at hyperactivesw.com
Mon Nov 18 15:13:17 EST 2013
On 11/18/13 11:45 AM, Graham Samuel wrote:
>
> My comment about conflicting error messages when I tried to open an
> inappropriate file still stands though: my guess now is that the
> "stack corrupted" is closest to correct, since the created file
> probably wasn't a stack file at all, apart from the extension.
They may not really be conflicting, even though they don't apply to your
problem exactly. If a stack was made in a newer version, which implies
the file format has changed, then an older version would see it as
"corrupted" when it tries to open it.
I was going to answer your question with a different suggestion until I
saw that you'd figured out what happened. But in case anyone runs into
something similar, I was dealing with almost the same thing yesterday.
In LiveCode 6, passwords changed. You can open older protected stacks in
6.x but once they are saved in that version, they can't be opened again
in an earlier version of LiveCode. I was testing an old-style text-based
cgi on my server which put a stack in use, and I'd saved that stack in
LiveCode 6.1.3. The ancient engine on the server has to be version 3.5
(boy I wish that would change) and it couldn't open the stack. It took
me a long time to remember why. I removed password protection in LC 6,
opened it again 5.5, and saved it there in legacy format. Then it worked.
--
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the use-livecode
mailing list