Paula Recchia 

The application seems to be trying the original source file here:

C:\Users\a.boi.INTERFAX\Desktop\TEMP\______pal 05.11.2023\SMS_Manuali\ProSSM_B A0454_Manuali_32_pretrasl GB-SPA\en-GB\2712_Coil Lifter_es_(TS)-tr.docx

Is it there?

Hi Paul, 

that route is on the Client's PC. I've already talked to him, I could send him the xsliff files and he could try to save the files on word (because I can't do it). Nevertheless,  it shouldn't work that way, I mean, I should be able to save the files myself, right?

Paula Recchia 

Paula Recchia said:

I mean, I should be able to save the files myself, right?

That depends.  If the original source file is embedded into the sdlxliff when the project is created, and this can be controlled by whoever set up the project in the sdlxliff filetype settings, then you will always be able to save the files yourself.  If the source file is just referenced (which will happen automatically if the source file is larger than the value set for embedding in the sdlxliff filetype) and then the sdlxliff file is available to you without the source file (as seems to be the case for you) then you may not be able to.

A lot of this is down to how the project is prepared and more importantly how the project is shared with others to work on it.  If the work is always sent as a package, and source files are not removed from the original project folder before sending the package (or even a zipped up folder or just sdlxliff files) then life is pretty much easy.  But as soon as you start to mess around and don't really know what you're doing then problems like this can occur.

Paula Recchia 

Paula Recchia said:

I mean, I should be able to save the files myself, right?

That depends.  If the original source file is embedded into the sdlxliff when the project is created, and this can be controlled by whoever set up the project in the sdlxliff filetype settings, then you will always be able to save the files yourself.  If the source file is just referenced (which will happen automatically if the source file is larger than the value set for embedding in the sdlxliff filetype) and then the sdlxliff file is available to you without the source file (as seems to be the case for you) then you may not be able to.

A lot of this is down to how the project is prepared and more importantly how the project is shared with others to work on it.  If the work is always sent as a package, and source files are not removed from the original project folder before sending the package (or even a zipped up folder or just sdlxliff files) then life is pretty much easy.  But as soon as you start to mess around and don't really know what you're doing then problems like this can occur.

Ok, I'll send your answer to the client.

It has already happened before and always with this client.
However, the error appears after a notification from onedrive 

Thank you for your answer

Paula Recchia 

Paula Recchia said:

However, the error appears after a notification from onedrive 

This is also problematic.  If the folder you are working with is on OneDrive and the OneDrive settings are moving files to the cloud instead of "Cloud and Local" you will only have a footprint on your computer that makes it look as though the files are there, but they are not.  So Studio will throw an error because the file isn't there.

I would recommend you do not work with files on OneDrive for your translation projects and never create your projects there.  I would also recommend you make sure that your OneDrive foldersare set to "Cloud and Local" to ensure things don't go missing (from your software perspective).

I personally think Microsoft have caused problems with the lack of controls available when using OneDrive as many software applications (apart from Microsoft of course) can have problems like this.  For example, I installed Camtasia on my personal laptop over the weekend and when I created my first project, which I tried to save in a OneDrive folder I got a message from Camtasia telling me not to do it as this could destabilise the project.

I think many software vendors, ourselves included, need to address this and make sure that users have more control over where the default folders are so that users can avoid using OneDrive for files that need to available at all times when working on projects.