Can't open file because it was created on an older version

[TCT]

Can anyone tell me how to access this file? It was made with an older version of affinity.

[Ldina]

I think the message says it was created in a LATER version, not an older version. You can open files created in an earlier version. So, you can open a file created in v2.4.2 with v2.6.2, but not vice versa.

[TCT]

you are correct. So there is no way around my problem?

[Ldina]

31 minutes ago, TCT said:

So there is no way around my problem?

Unfortunately, Affinity programs are not backward compatible. But...You can install the Beta version and use it to open your file. Once open in the Beta, you can highlight and copy all the layers (Cmd-C), then open your older version of the software and paste those layers back into the older version. Since it was created using an older version from the start, all the content you copy should paste without any issues. You can also do that if you have a commercial release that is more current than what was originally used to save the file.

I think you'd need to have an account with Serif Affinity and sign in to your account. The beta versions are completely separate programs from the commercial releases, so they would install as separate programs and you can have commercial release and beta versions open at the same time. If you make any edits to the file in the Beta or a later commercial release, and then save the file, you'd need the same version or later to re-open it. It's worth trying, especially if it is a large, complex or important file, or you have a lot of them. Here's a link to sign up for the beta program. You can be as involved (or not) as you wish to be with the beta program. 

https://affinity.serif.com/en-us/affinity-beta-program/

[R C-R]

2 hours ago, Ldina said:

Unfortunately, Affinity programs are not backward compatible. But...You can install the Beta version and use it to open your file.

From the screenshot it looks like the OP is using V1 of AD. From your link to the beta program page there is this in the Who can participate? section:

Quote

Our beta program is available to anyone who owns V2 of our apps.

So the OP may be out of luck with the beta....

[Ldina]

@TCT what version of AD are you using? I have AD v1.10,8 installed and v2.6.2. If you only have one file to convert, upload the file and I’ll give it a shot. As long as the file doesn’t contain any features incompatible with v1.10.8, it should work. You’d need v1.10.8 to open it, assuming it works.

[concha]

Well, this is not true, I mean, I´m not able to open a file made with an EARLIER VERSION! Isn´t it a very strange thing? 

[R C-R]

4 hours ago, concha said:

Well, this is not true, I mean, I´m not able to open a file made with an EARLIER VERSION!

Are you sure about that? Is this a file you created or did it come from some other source? Can you provide this or another file that shows that error when you try to open it?

[Alfred]

1 hour ago, R C-R said:

Are you sure about that?

The error message clearly refers to an earlier version (“una versión anterior”).

[walt.farrell]

5 minutes ago, Alfred said:

The error message clearly refers to an earlier version (“una versión anterior”).

But we know that it is intended to mean "from a later version", so I suspect a translation error from the English, and possibly by someone who also doesn't understand the meaning of the English word "anterior" and thinks it means "later".

@concha: You might switch Affinity to using English for its User Interface using Edit > Settings, and see what the error message says then. Here's what I see, for example:

1. Opening a file saved with 2.6.3 using 1.10, with English as the interface language, on Windows:
   
    
2. But here's what I get performing the same operation with Spanish as the interface language:
   

 

[mopperle]

Such errors can happen. My daughter (she studied spanish) told me, that a more correct translation could be:

„El archivo incluye características de una versión más reciente de Affinity“

[Oufti]

16 hours ago, walt.farrell said:

I suspect a translation error from the English

Reported in the Bugs section: