Hello I'm wondering how best to manage the item storage needed for PDM users to run SolidWorks properly. Do you manage everything on the PDM, on your company's network, a mix of both? The idea is to have the + and - of your solutions. Non-exhaustive list:
For us, it's a mix of the two. All the configuration (document templates, blocks, material database, drilling assistance database, basemaps, macros, etc.) is on a server accessible to all users (same for the sldsetting file which must be read/write access anyway). In the vault, we only manage the files and a few templates related to features specific to Solidworks PDM (creation of a specification in Word format from a template stored in the vault).
With us everything is in a PDM directory named 'library' with systematic synchronization when opening PDM for this directory. It allows you to manage versions of your files, parameters, templates, drawings... (and therefore prevents anyone from making a mess of these crucial files). Only the sldsetting file is local for each workstation (but this is still a modification of the sldreg that is in the vault).
Hello just as @froussel everything is in EPDM for the same reason as him, Automatic synchronization is essential in this case. Only the "sldsetting" files and those related to the "smart property" are outside PDM
Ok thank you for your feedback. And do you block access to these files to users to avoid unfortunate changes or is it open to everyone? For example, with the material base or block models for drawing.
Hello The material database must remain read/write accessible to my knowledge, so incompatible with operation in the trunk. For the rest, as our IT department does not go below the main directory to manage rights, I have made the files I want to secure read-only.
Hello @Cyril.f With us, the basic materials are in the trunk and it works. it just needs to be extracted when creating a new material (or modification of an old one).
Hello It may have changed because I remember that at one time there were messages related to a write access request on this file if only to access it. As we have had the trunk since 2009, we have kept this way of working.