MattBirk
-
Posts
6 -
Joined
-
Last visited
Posts posted by MattBirk
-
-
@IanSG @walt.farrell so, i'm to implement a version management or other systems to work in an application that doesn't lock files? the fact that two people can open it at the same time provides absolutely no value if it won't allow both users to save their work in the original file. hard to believe an issue like this should be kicked back to the client to figure it out, with a workaround no less. i've been a cio for over 25 years and have never had an application that would allow two people to open it and edit it without both of them being able to save to the original file.
sorry for the rant but this is really crazy that an app doesn't use the o.s. to lock it's files. unless there is value in it it should be changed to work correctly.
-
@John Rostronthat doesn't work for a company. We are not home users. We cannot copy to local and leave our secure corporate network - that would be crazy ☺️. In addition, User B can still open and edit the file if left on the corporate network and what would be the purpose of allowing two users to edit if we have to jump through these hoops. The fact that it's allowable is what is questioned as it serves no purpose unless both users can save much like onedrive operates. Any other version stuff is a workflow that just does not work.
-
update: The file is on our corporate network. Two separate win10 pro computers can open the same Publisher file. User A and User B work in the same file without each others knowledge. User A gets finished editing and saves with no indication that User B worked in it also. User B then saves but gets a dialog that the file has changed and asks if they want to SaveAs or Replace. If User B selects Replace then User A's changes are gone and User B wins. The last person to select Replace wins.
We tested the same in Photo and got the same results. This is really bad and needs addressed by Affinity. We'd prefer the file to be locked and one edit at a time.
Affinity - What say you?
-
@iansg I'd think that shouldn't be possible for two people to edit the pub file at the same time. if it's by design to allow that then i'd like to know why the second user cannot save. the error they receive is:

-
We have a document in publisher that two people can open at the same time and one cannot save their changes. the other person can save but we lose work from the other. they cannot saveas either


two people open pub file and only one can save
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
@Wosven @R C-R We only want the Affinity files to lock once a user opens it. Remote, On prem, Server, Local, should not matter. These applications should work the same as other applications such as O365 Word, Powerpoint, Excel, Adobe CS Photoshop, etc... (and almost every other app on this planet).
We are a firm with 5 offices and have the infrastructure in place to effectively work together on all aspects of a project whether you are in an office or at home with zero issues accessing files. Overwriting someone else's work is (was) a thing of the past until this issue appeared. Yes, it's user mistake by selecting Replace on the file but there should be no chance for this to happen and lose work.