virtualized assemblies

[Dum]

Good morning to all,
I would like to try to undergo a very disturbing problem that is manifesting occasionally but that, in addition to the discomfort of the loss of time, it is taking away my sleep because I do not understand why.

for years now that I use for the whole part of commercial the function of virtualizing the components.
It happens, rarely but it happens, that sometimes the cylinder that opened me quietly the day before, the next morning you no longer find links to the parts that should be saved internally and then open it "empty".
the tree is there but it is as if all the components were "disactivated".
He asks me to force the search inside a folder, he suggests that backup.
Now, being saved internally, not even a search by name saves me.

has it ever happened to you?
Did you manage to solve this?
I have no mathematical certainty, but it seems to me that the problem materialized when I installed the third version of sw (now I work on 2016/2017), but I strongly doubt that it is a question of versions that punch.


Now I have to download the component again, make the configurations, give it all the couplings on the general axieme. .

Have a good day! !

 

[MassiVonWeizen]

It never happened to me.
Have you tried to load a backup version of the axieme?

is not the solution, but when you make virtual components save them externally and put them in a secure folder from possible references maybe zipped so you are sure they will never be taken into consideration), at least avoid having to remake them

 

[Dum]

Hello Mass, first thing I tried to do. .
but nada, even the back up is "failed". .

It bothers me because I don't understand why, it's out of every logic of operation. .

 

[MassiVonWeizen]

I will try to do some research if it is u problem known

 

[Dum]

I tried to do an internet search. .
but I'm wrong with the search terms or it doesn't seem like a "note" problem.

and clearly I happened this morning, and time to close and reopen I had missed another component.. :

 

[MassiVonWeizen]

you have to do research with English terms because in Italian, apart from this site, there is little more.
I usually do this:
I write generic terms that circumscribe the problem and insert in the search the stinga site:forum.solidworks.com, then I try to refine the experiential terms in a cask of culko

 

[Atreiou]

My experienxze, useless to help you unfortunately, is that's why I stopped using virtualized objects. . After months you opened the assemblies and the parts were gone...
so when I have to change a library object, which was my case, I save it first locally in the project folder.
mine is hydraulic welding fittings, curves, tees, etc.

 

[Dum]

to me it worked well for years.
In the last 2/3 months, he's fucking me. . .

 

[MassiVonWeizen]

only with 2018 or all versions?

 

[MassiVonWeizen]

https://forum.solidworks.com/thread/211756

 

[Dum]

only with 2018 or all versions?

now with 2018
for 2016 I use a customer's library, for 2017 I don't need libraries as lclient does not have any particular requests, and what I need I go to get it from the first versions of the library.

It's a library I've been carrying for years, every version change I make a copy and I only use it for the latest version.
and said that, I'm attached to your message, of which I thank you,

https://forum.solidworks.com/thread/211756

because I think that to read the content, the problem arises to all those who update the library.
perhaps in the passage between one version to the other is "eat" some components.
that could also be plausible, if it were not that in the evening I open everything correctly, the morning after the same set presents virtualized components with errors.
Tonight at home I read more calmly and I see how they are put in iuesei.. :

thanks, as usual, for the interest.