Understanding File References 2

[brrian]

We've recently switched from Mechanical Desktop to SolidWorks. The switch has gone reasonably well--my users enjoy modeling in SolidWorks, but some are having a difficult time understanding file references. In Mechanical Desktop parts, assemblies and drawings all live in one file, so there's nothing to manage. Now they must pay attention to the references and understand what happens when they (for example):

-move a file
-rename a file
-copy a file

Some don't understand why it's safe to rename a drawing in Windows Explorer, but not a part. Others struggle with "Save As" vs. "Save As Copy."

Is there a document, website, book, presentation or otherwise that explains file references in layman's terms--sort of a "File References for Dummies"? I'm considering writing one myself, but I'm hoping to find something that does a better job than what I can do. It doesn't even have to be for SolidWorks--Inventor (ugh) basically manages files the same way, so I could start with something written for Inventor.

Have any of you had a similar situation--users who struggle with file references? I'd also be interested in knowing how you handled it.

Thanks in advance,

Brian

 

[CorBlimeyLimey]

macPT ... I agree with you, those two things are SW Explorers weakest points. However, instead of selecting the assembly model, if you select the top level (assy) drawing, the drawing & all the parts/assys will get copied.


Making the best use of this Forum. faq559-716
How to get answers to your SW questions. faq559-1091
Helpful SW websites every user should be aware of. faq559-520

 

[ctopher]

I agree SW Exp needs a makeover, but is the cleanist way to go for now.

Chris
Sr. Mechanical Designer, CAD
SolidWorks 05 SP2.0 / PDMWorks 05
ctopher's home site

FAQ371-376
FAQ559-1091
FAQ559-716

 

[rgrayclamps]

Hi, Folks:

SW external file references are nothing but certain of design intents in your part and assembly documents (models or drawings). There is no danger at all. It is all up to you whether you want to use them (the design intents) or not. Many of statements in this thread are misleading to some of new users. In my opinion, the real danger is that many users do not have secured vaults. As long as your documents are secured through network security, users can do whatever they want to do regarding these design intents (file references).

You do not have to use any PDM in multiple user environments. You do not have to use either SW Explorer or Window Explorer. What you need is a discipline to setup a secured vault at your network plus a master list of your documents (of course, preferably in a sequential order) and BOM. With your SW documents secured, you can freely move, rename, copy anything you want. We have 10 seats of SW, but workflow is nice. But two years ago, it was chaos because we simply did not have a secure vault.

Alex

 

[SBaugh]

rgrayclamps,

So are you saying it doesn't matter if a user changes the name of a file in either WIndows explorer or SW explorer, even with in-contexted designs?

If so you are sorely mistaken. You think it's because of unsecured vaults... I think this is more misleading then anything here no matter how new of a user you are. What does having unsecured vaults have anything to renaming files?

Please Elaborate further.

Regards

Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.scottjbaugh.com

faq731-376
faq559-716 - SW Fora Users

 

[rporter]

brrian

Like you we are a made to order Company. We will make copies of parts that are close and put them in a new project. We had used windows explore for doing this but have changed to SolidWorks explore for this task we copy both assemblies parts and drawings that are needed for the new project. The major reason for we changed from windows explore is we had some major problems when a few times someone was in a drawing and opened the part from that drawing "right mouse click on the part name and click open part", they made changes and same everything. This would have been ok but they forgot to change the part referanced that the drawing referanced. SO the part change in an entirely diffrant project and you can about guess what happend when the original part was manufactured.

If you rename a drawing and are in a part and want to open that drawing from the part you will not be able to becouse the part no longer knows what drawing it is assosiated to.

I hope this is understandable.

Roger

 

[rgrayclamps]

Hi, Scott:

With existing SW documents secured, they won't be affected by any accidental changes. If a user needs to revise a document, he or she needs to go through revision process.

I am not saying it does not matter if a user changes the name of a file in either Windows Explorer of SW explorer. If the user needs to changes the name of a file, he or she need to go through revision process to its parent assemblies. I feel there is no need to use Windows Explorer or SW explorer at all.

Unsecured vaults are dangerous and unsafe to renaming. When a user needs to create a document (whether be part or assembly document), he or she needs to search through the vault to see if this document already exists, or if there is one he or she can use a template part or assembly. If a similar one is found, the user can do anything he or she wants, because the user is going to create new documents.

I am not a new user myself. I have been using CAD for last twenty years. I have been using solid modelling during last 8 years.

Thanks for your feedback!

Alex

 

[ctopher]

rgrayclamps, If I understand you correctly, it sounds scary. To me it does not sound like very much control over the SW files. But, if it works for you, that's great.
Just curious, How long have you been using SolidWorks?

Chris
Sr. Mechanical Designer, CAD
SolidWorks 05 SP2.0 / PDMWorks 05
ctopher's home site

FAQ371-376
FAQ559-1091
FAQ559-716

 

[SBaugh]

Not everyone is running a PDM software or PDMworks for that matter. It is happening more that people are using PDM software, but when you have in-contexted relationships in an assembly to a part, then renaming it very important in how you proceed with it. Because those of us that are or have done automation with SW in the past have found this out hte hard way. Renaming files can be bad when you do it outside of provided software.

I'm not a new user to CAD myself. Been working in 3D CAD for the past 11 years, 1-2 years in 2D CAD. Been working with SW since 96.

Regards,

Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.scottjbaugh.com

faq731-376
faq559-716 - SW Fora Users

 

[rgrayclamps]

Hi, Chris and Scott:

I have been using SolidWorks since SW 98. Before that I used SDRC IdeaMaster for a couple of years. I also happen to be a part-time database programmer.

Actually, renaming part or sub-assembly models within SW is quite efficient. I have tried all the following three methods:

1) Renaming thru. Windows Explorer;
2) Renaming thru. SW Explorer; and
3) Renaming within SW.

I found out that the last method is the most efficient as long as your existing documents are secured and you take object-oriented approach. Object-oriented programming is a foundation of SW. It means a user processes a document at a time. I just can not imagine that users open unsecured documents and try to save as different part/sub-assembly/assembly documents.

I totally agree with Scott that renaming files can be bad when you do it outside of provided software.

Always enjoy reading your comments.

Alex

 

[macPT]

CBL

The problem is that the drawings of parts and subassemblies are not processed. So the work is half done!

Have you abetter idea?

Regatds

 

[CorBlimeyLimey]

Javelin Technology has an add-on called Copy Project under their "JavWare" suite.
Check out

http://www.javelin-tech.com/main/products/javware.htm

Making the best use of this Forum. faq559-716
How to get answers to your SW questions. faq559-1091
Helpful SW websites every user should be aware of. faq559-520