Hello Greta Magyar,

Thank you for your quick response.

Our file-based (local) projects are located in our network server. Each SDLPROJ file is located in our client-based network server structure along with the project source and target folders. People access the project using that SDLPROJ file. Everyone uses the same file to access the project when they have to complete a task for that project.

Even after removing the project from the list, closing Studio and rebooting the machine, the added file is still not visible.

We do not add files into subfolders. We use the Add Files feature straight from the Project or Files views of Studio. I've checked in one of our problematic projects, and they don't contain subfolders.

I understand that file-based projects were not meant to be shared by several people, but until we upgraded to 2019, it worked adequately for nearly 2 years. This is why I was inquiring. I figured the GroupShare project management module would probably solve that issue.

Thank you for taking the time to answer my question!

Regards,

Antonie, C. Tr.

Hello Greta Magyar,

Thank you for your quick response.

Our file-based (local) projects are located in our network server. Each SDLPROJ file is located in our client-based network server structure along with the project source and target folders. People access the project using that SDLPROJ file. Everyone uses the same file to access the project when they have to complete a task for that project.

Even after removing the project from the list, closing Studio and rebooting the machine, the added file is still not visible.

We do not add files into subfolders. We use the Add Files feature straight from the Project or Files views of Studio. I've checked in one of our problematic projects, and they don't contain subfolders.

I understand that file-based projects were not meant to be shared by several people, but until we upgraded to 2019, it worked adequately for nearly 2 years. This is why I was inquiring. I figured the GroupShare project management module would probably solve that issue.

Thank you for taking the time to answer my question!

Regards,

Antonie, C. Tr.

We have the same setup. Newly added files don't appear to others, although they are visible in the folder. Problem still exists in Trados 2024!
Apparently GroupShare and now Trados Cloud is the solution..., but I prefer to create new Trados projects for the new files.

Jérôme Pott 

Did you run any preparation tasks on the files? Are the extra files in an additional folder?

I dragged and dropped the files and used the default settings. Everything looks correct on my side, but my colleagues don't see the newly added files in Trados Studio, but they do see generated xliff in the folder on our server. They can also double click the xliff to open it in Trados.
Restarting Trados, removing/readding the projects didn't help.

Jérôme Pott 

Do we talk about local Trados? In this case the project file *.sdlproj is on your PC, not on the server I would suppose. Could you please write more about how do you work with your colleagues?

Yes, local projects, but hosted on our company server. It's like Trados doesn't refresh its file view.

Is there a way to force Trados to refresh the projects and files view? I remember something about deleting a config file in temp folder.

Jérôme Pott 

If you create a project on the server, the sdlproj file should also be created there. Then when you add files, it also should be changed there. But if the file is also open in other instances of Trados, I do not know what happens then. Maybe you could test the following: let your colleagues remove the project from their Trados instances. Modify the project by adding files and the let the open the project again.

I do not work that way, all my projects are on a NAS. But from what I remember, the changes done to such project with a laptop while the project file also being present in the Trados instance on the desktop were not visible. Trados Studio is designed to work locally and not to be shared via a file server.

Yes, I guess that local instances of Trados don't register the changes. I tried what you suggested, but to no avail. They even rename the Trados project folder, but it didn't work. But what's strange is that for some colleagues and some projects and suddenly worked. Anyway, I'll keep creating new Trados projects if new files come afterwards. Thanks for the help!

We're planning on moving to Trados Cloud once it's more tightly integrated with Trados Studio (the current Manager tab is not good enough for us) or when the Cloud Editor attain feature parity with Trados Studio.