Hi all.
My colleagues and I are faced with a problem.
We have created a file of custom properties for the elements from a list of welded parts (sheet, mechanically welded profile etc...), it works very well except on one workstation.
Version and SP identical to the others.
I am attaching the message displayed when you try to use it.
Thank you in advance to all.
Hello.
Stupid question but ... Is it normal the " ." (period) after the wldprp? isn't that what causes problems for the access path?
Hello,
No, that's just the point to finish the sentence. 
Good evening
Yes, we all point to the same file.
In fact he writes only a few properties, while on all the others it appears in full.
We have links to excel tables
Why not share them from a server?
This helps to avoid these kinds of problems...
That said, I prefer @FRED78's remark, it's most likely a redirection problem from the Solidworks options:
more directly I think the path is incorrect (to check in the Windows explorer):
c:\user\y.vallespir\desktop\propfinal.wldprp
=> Not well The " Point " of " y.vallespir "! (some software will not accept it...)
And it is surprising to find a " desktop " directory there...
We also have duplicate properties.
Normally when it is managed by the editor, there is no duplication possible, unless there is manipulation in the properties of the part or assembly. When there is a duplicate, SW does not display anything.
The case came to us via properties on the bodies of a part + the properties of the editor, so to check
Hello
It's on the server, we put it on the desktop precisely to eliminate the hypothesis that it's a server access that is blocking.
Thank you
We tried to create a simple part without touching anything and the form is still not displayed in full, it blocks from the list of choices.
Hello @Samuel_FAUPIN
It's surprising to see only one part of the properties, which is that the links are good.
You have checked
, that you are pointing to the correct properties file.
Tried to replace it with a file from a workstation where everything works.
If the problem persists, I will personally start from a new database, by merging a new file with the editor.
Indeed the path of is not the same as on the other workstations yet in file location we have specified the path that the on mine, however I wonder if this does not have a correlation with the search paths, which by the way is impossible to delete.