Works fine for me. Maybe it was fixed in SP3.
Hi Kelvin, Thanks for the reply.
- So to clarify, you have "No Preview During Open" selected.in the System Options
- You have an assembly that can't find a part (it was deleted moved or whatever)
- You dbl click on the assembly in explorer to open it and you get the dialog that ask you if you want to browse, suppress...
Currently in SP2 the only way I can get this to happen it to uncheck the "No Preview During Open" option. I have no problem with doing so but I thought I would see if anyone else has seen other issues with it unchecked.
If it works in SP3 with it checked the would be better yet. Got a little nervous though when I saw all the issues in the KB with it checked so I may have a dozon or so users uncheck it for a week before having the masses do it.
Thanks again for your reply.
I'm sorry. I must have been doing something differently. The sequence you describe results in the missing dialogue box in both SP2 & 3.
One workaround is to drag & drop from the Windows folder.
Thanks for checking. Thanks for the workaround suggestion as well. Since dbl clicking is a basic windows functionality and utilized by multiple applications I rather not try to change all of our users habits for the sake of a bug in SolidWorks. I will be pursing unchecking the "No preview during open" setting. I am guessing by the lack of replies nobody has run into any major ill affects with having this setting unchecked.
Thanks again for your replies,
The failure to check with the user whether to find files or suppress them, in favour of the second course of action, is still a problem in SW2016SP4. This is not just when you open from Explorer; it happens when you open from within Solidworks also.
Although this thread nails the solution, we had to come up with it independently, because the title of this thread refers not to the problem, but to the solution, and the content of the thread does not include the text of the missing message. A case of having to know the solution in order to find it....
To save others going through the same process, I'm going to post more comprehensively under the existing thread