Does SW tend to have issues with UNC paths? I have some assemblies that when I open them have a part or assembly suppressed. When I unsuppress them, SW asks if I want to find them. Click Ok and I am placed into the folder where that part/assembly is. Seems to be either a bug or perhaps there is a setting I have forgotten about.
Updates from RodUding Toggle Comment Threads | Keyboard Shortcuts
-
RodUding
-
RodUding
I am having issues with PNG image in my drawings. I have the company logo as a PNG image in the sheet format for all of our drawing templates. When I create a new drawing, the logo shows up. After I save the drawing and open it later, the image is not displayed. However, if I edit the sheet format, I can click the area where the image is supposed to be and I get the property manager for it and the outline shows up onscreen. Any clues as to what is going on here?
-
Chris Serran
I ran into this issue a while back, I’ll just post the reply from our VAR, it seemed to help:
“I believe that sketch pictures were designed to work in sketches. Since the option is available in drawings, and I confirmed this issue with assembly drawing, I will check with SolidWorks about it.
To insert pictures in drawings, we typically use Insert, Object – Create from File. Sometimes this option does not work correctly due to Windows OLE limitation, and in that case there is a simple workaround: a picture is inserted in a document such as Word, copied and pasted on the drawing. I have attached a drawing with the small Waterous logo inserted this way; the big logo was inserted using Insert, Object command.”
-
RodUding
Hmmm, this is interesting. Previously the image was a bitmap, a huge bitmap that made the template files 2MB in size. I replaced it the PNG to reduce the size. I inserted the new PNG file using the Insert>Picture. I wonder if there is a difference between Insert>Picture and Insert>Object?
-
Chris Serran
I’m not too sure but it’s something I’ll test out.
My templates are around 2mb as well and it’s a PITA having such large drawing files.
-
-
RodUding
Does any one have problems with SW randomly crasihing when inserting parts or sub-assemblies into an assembly. The crashes will occur whether I pull from my C: drive or the network.
-
mattl
Rod,
No, I haven’t seen any random crash problems.
-
solidsmack
I’ve seen this in 2009 SP0 and 1 when there is a conflicting external file referenced. meaning, a part being pulled into an assembly is coming in read-only when it should not be.
I had a drawer assembly, with drawer slide coming in as read-only (it will say ‘read-only’ when you select to open a part and click the references button.)
I have to repoint the reference manually and then when I drop the assembly or part in the assembly it will not crash.
-
Doug
Yes
When I open a ass and select one of the part or ass to edit. If I tab back to the ass bommmm -
RodUding
For me, it is totally random. I might insert 20 or 30 parts in a row just fine. Then have it crash, restart and be just fine. This occured mostly in 2006 and 2008. Since we skipped the 2007 version, I have no idea how it would have performed. I will have to be sure to check the read only status on the parts and assy’s that it crashes on the next time.
-
-
RodUding
I have an assembly that has parts that refers to a coworkers desktop location. Each time I try to change the references from the open dialog box, I cannot scroll down farther than about 3 screens and it stops. Any suggestions?
-
admin
I would use the SolidWorks explorer in this case, it is a workaround, but it should work.
-
CBL
Does it stop at the co-workers referenced parts?
-
RodUding
It stops at the 1st part. When I go to our Parts folder which has all the reference parts in it, click Ok, it continues loading the entire assembly.
-
afee451, and 
Chris Serran and 
Doug, 
CBL, and 
gupta9665 11:25 pm on December 14, 2009 Permalink
Did you renamed the part or the assembly by any chance.
afee451 7:18 am on December 15, 2009 Permalink
Because you are discussing a UNC path I assume you are working with files being shared on a network. Its been my experience that all windows programs can get a bit flaky accessing network folders. Most programs, Soldiworks included, will be much more well behaved if you map the folder as a network drive and then use the “local” path.
RodUding 9:17 am on December 15, 2009 Permalink
The parts were not renamed. They are located on a network that has “issues”. I am in a constant battle with IT who say they do not see “issues”. It may be possible that something is flaking out on the UNC paths but not on the mapped paths.