solidworks, file list, properties and access database

[drake]

Thank you, jenuary!
works perfectly so and you avoid remaking the process.
One thing I ask. if I take a part in which the custom property has already been written with your macro and the cup x use it in other together. Of course, there is no dependence on the parts. when I launch your macro into the new set supersedes the value it finds?

ps:
I don't understand the utility of putting the two types of rescue. when you save you (.) sometimes you find in sw some hidden thighs that leave you, at least puzzled... .

 

[jenuary]

Thank you, jenuary!
works perfectly so and you avoid remaking the process.
One thing I ask. if I take a part in which the custom property has already been written with your macro and the cup x use it in other together. Of course, there is no dependence on the parts. when I launch your macro into the new set supersedes the value it finds?

the process eliminates the property before rewriting it so there is no problem.

 

[teseo]

I would propose a general applause for jenuary who is doing a lot of very comfortable macros.......:finger:

 

[drake]

applause of 10 min!!! !

 

[drake]

hi jenuaruy, I press that the macro is perfect like this, but I ask you this...
if in a project you make use of components saved in a library folder, the macro goes to change these by adding the custom property to them too?

 

[jenuary]

Yes.
There is no distinction between library component and component in the work manager, we always talk about a .sldprt file where we go to write inside.
for this sw does not associate the quantities to the individual components, because it considers it a property together, it is the task of the user or the pdm to count them and manage the distinct (it would be the correct management of the assemblies).
for me and for others, which we provide third-party design, each contract is independent and therefore I have no problem, putting into the table recovery the properties of the component by linking me to the quantity.

 

[drake]

I realized that's what I thought. I wonder if instead it was possible to make sure that the macro only acts in the components within the workbook, xché x come tu, also x me every job is independent from the others... It could be a problem to write within a library component, because if it has already been used, as it is assumed, and the tables of a given job were made, at the time of a possible opening them x do other prints, you risk printing the new tables with incorrect values of instances. Don't you think?
Thank you.

 

[jenuary]

It's a possibility.
at that point it must be assumed that any component outside the work director of the axieme in which the macro is launched is a component of the library, which is not said to be so, because I could have the general axieme in a director and under axiemi (moduli) on under folders.
In this case you have to have everything in one folder.
some stakes must be put. . .

However, there is a possibility to check if a component is a toolbox, but I don't know if "bookshop component" is exclusively toolbox for you.

I will see to create an alternative version of the macro, but you will have to have some patience due to the coming vacations.

 

[drake]

It's a possibility.
at that point it must be assumed that any component outside the work director of the axieme in which the macro is launched is a component of the library, which is not said to be so, because I could have the general axieme in a director and under axiemi (moduli) on under folders.
In this case you have to have everything in one folder.
some stakes must be put. . .

However, there is a possibility to check if a component is a toolbox, but I don't know if "bookshop component" is exclusively toolbox for you.

I will see to create an alternative version of the macro, but you will have to have some patience due to the coming vacations.

we could put a stake like that.
library I mean any component not only toolbox. you could do that you write the custom property to the main workbook, the one in which the axieme is contained with which you launch the macro and check the presence of any subfolders and in the affirmative case write the property also to the internal components to these. but, if possible, I would personally avoid doing it to components outside this folder. She'd be a pretty, but she could do without it. Besides, when I use library components I save them from time to time in the various workbooks even if so I create several scripts in the disk. but with all the space of today's disks I prefer to do so rather than change something dullly.
Thank you.

 

[jenuary]

we could put a stake like that.
library I mean any component not only toolbox. you could do that you write the custom property to the main workbook, the one in which the axieme is contained with which you launch the macro and check the presence of any subfolders and in the affirmative case write the property also to the internal components to these. but, if possible, I would personally avoid doing it to components outside this folder. She'd be a pretty, but she could do without it. Besides, when I use library components I save them from time to time in the various workbooks even if so I create several scripts in the disk. but with all the space of today's disks I prefer to do so rather than change something dullly.
Thank you.

I attach the modified macro with the addition of the option.
test it on a full set for safety.

 

[drake]

I attach the modified macro with the addition of the option.
test it on a full set for safety.

grazi jenuary lo farò!

 

[drake]

I tested the new macro on a set of 1300 components and worked perfectly not writing any custom properties in objects outside the axieme folder.
Thank you again!

 

[teseo]

Good day to all,

I apologize if I reopen this old discussion; Today I was using the jenuary macro, which I used several times with perfect results, but today strangely I did not get a correct result.
I have a small set of 10-15 parts. all smooth row for parts without configurations but with a configuration part does not count correctly.
going to analyze the thing I see that the amount property(I use npezzi) does not write it to me in the configurations of the component but only "in the custom card" in the "specific configuration card" does not write anything.
In addition the pieces in question should be 8 (7 of one configuration and one of the other ) but in reality he counts 7.
Now I ask the macro does not predict configurations? Did you happen the same thing? Did I set something wrong?
I attach an image....

thanks to all

 

[jenuary]

If you can post the aid, I try to check where the problem is or the limit, send it to me as private.

Hi.

 

[teseo]

If you can post the aid, I try to check where the problem is or the limit, send it to me as private.

Hi.

View attachment deposito macro.rarHello there

Hi.

 

[jenuary]

View attachment 45695

ciao eccolo

ciao

Hi, Teseo.
the macro with which you worked went to write in the tab "personalized", the one that I allego modified and writes in the configuration properties.
Test it if you do what you need.

Good day
jenuary

 

[teseo]

Thanks jenuary you are really too kind.... .
I'm sure thank you again.

 

[-Mc-]

I reconnect to the discussion for a question on sw;
can you compile a field of properties of each sw file so that from the resource explore you can have the field description displayed?
the goal is to have, in explore resources, leaving the pdm lost:
file name, size, last edit date, description.
I noticed that the title field can pop up and display in the resource explorer.
I would like that from sw, the title field to be compiled automatically (magari via string) fishing the description from the custom property card that I use to fill out the cart.

 

[MassiVonWeizen]

viewable tags in explore resources are those in the details tab of the properties of the resource explorer file
these tags are present and compiled in the tab synthesis of solidworks file properties.
instead of description there is the comment voice that could serve the same purpose
strings work on properties customise, on board synthesis non lo so.

 

[MassiVonWeizen]

for the title field see if you can use this discussionhttps://forum.solidworks.com/thread/55291