Wrong error messages

[design punch]

Hi,

this is not an new problem special in 1076, but still last in 1076...

A Publisher file contains placed images (afdesign, vectors etc.), made by AFDesigner.
If you open the AFDesign file in Designer and the publisher file in Publisher, modifying the AFDesign file in Designer and save it, then switch to Publisher (alt + TAB), everything is ok, except Publisher produces almost every time wrong error messages like: corrupt file etc. (One can ignore them, because they are not true ...)

 

 

 

[Alfred]

1 minute ago, design punch said:

this is not an new problem special in 1076, but still last in 1076...

If it isn’t a problem which is specific to beta builds, it should be reported in the main Publisher bugs found on Windows forum.

[design punch]

sorry,

and how to move it now ??

[Wosven]

Hi,

I think it's the same problem:

 

[StuartRc]

Yeah it does look familiar!...Just found another issue! 
 

[StuartRc]

Interesting just tried the same process in APub Beta. and you get the same result

1. open the AD file (special with links/beta)
2. edit the linked file save it= alert box as below
3. Undo the process and filetype not supported alert box gets activated even though it updates the file when you return to the previous tab..

 

[StuartRc]

2 hours ago, Alfred said:

If it isn’t a problem which is specific to beta builds, it should be reported in the main Publisher bugs found on Windows forum.

Normally you would be quite correct....But...just tested files the in AD beta and Apub and getting the same/similar results

[Alfred]

25 minutes ago, StuartRc said:

just tested files the in AD beta and Apub and getting the same/similar results

Do you mean only AD beta, not the current retail version of AD? And do you get the same results (or similar) in the retail version of APub? I understood from @design punch’s post that although it’s reported here against APub beta build 1076, this is a known problem. If it only occurs in beta builds then of course it’s in the right place.

[StuartRc]

1 minute ago, Alfred said:

Do you mean only AD beta, not the current retail version of AD? And do you get the same results (or similar) in the retail version of APub? I understood from @design punch’s post that although it’s reported here against APub beta build 1076, this is a known problem. If it only occurs in beta builds then of course it’s in the right place.

Both unfortunately!.. It occurs across versions...AD/ADBeta/Publisher Beta (as above) just by repeating same process in different versions with the same files.  I had not tried it in the beta until this thread....with hindsight I should have set up a much simpler file and tested with that....I picked up the issue when assembling Camouflage III..it can get a bit annoying...I went back to using embedded files!

[Alfred]

7 minutes ago, StuartRc said:

Both unfortunately!.. It occurs across versions...AD/ADBeta/Publisher Beta (as above) just by repeating same process in different versions with the same files.  I had not tried it in the beta until this thread....with hindsight I should have set up a much simpler file and tested with that....I picked up the issue when assembling Camouflage III..it can get a bit annoying...I went back to using embedded files!

Thanks for confirming that it’s not a new (beta only) thing, Stuart! In that case, as I said, it should be reported as a continuing problem with the retail versions.

[StuartRc]

Just now, Alfred said:

Thanks for confirming that it’s not a new (beta only) thing, Stuart! In that case, as I said, it should be reported as a continuing problem with the retail versions.

No it's definitely not a new beta only thing...I hadn't checked Publisher until tonight..

[Wosven]

I had this problem while using a beta that is now a retail version.

I suspect the problem occurs when an app try to read a locked file the other app is saving, or when the file is only partially written (not reconized/corrupted file).

[Pauls]

I've added this report to the issue - thanks