multiple users working on parts of an assembly

[Tmoose]

This gives us un-ending problems. "Opening as a copy" appears the only option if somebody else gets to the assembly first, and that prevents proper updates.
Is there something we are missing?

 

[drawoh]

Tmoose,

SolidWorks perfers to have write access to all the models in what ever it is you have loaded. This is awkward, and I recommend turning the feature off.

Pull down Tools->Options...

When the window comes up, select the System Options tab and click on External References. Turn ON the button for "Don't prompt to save read-only" referenced document (discard changes)".

Now, SolidWorks will not complain when you use read-only files. This allows you to work with other designers. It allows you to treat existing parts and assemblies as a design library.

The first guy to load files gets write access to everything that is writeable. You can ensure that the guy who uses the top-level files comes to work late, or, you can do something with the ACLs (permissions) in Windows. Take a look at the file properties in Windows Explorer.

JHG

 

[TateJ]

If you have users independantly changing parts of an assembly on a regular basis, then you have bigger issues here.
You need to make sure everybody knows when to exit & re-open their assemblies so they get the most recent parts.
I don't think there is a workstation-based modeling package that would handle that sort of real-time update of assembly parts.
Maybe there are main-frame engineering programes that do - but this is out of my realm of experience.
With SolidWorks - only one person can have the part or assembly at a time.

tatej usfilter.com​

 

[brengine]

Somewhere in the Tools\Options there's a "Open Referenced Documents with Read-Only Access". At least that way whoever opens the main assembly first doesn't get write access to ALL subassemblies and parts...but I think you have to explicitly open a part with Read/Write access (I forget for sure). I can't remember the particulars but maybe this'll help (we haven't had this issue since we got a PDM).

Ken

 

[automationbabe]

Used to have the same problem at my last company.
We opened assemblies with all parts loaded with read-only access. If the parts are open for "Read-Only", you can reload them with write access, if you need to make a change. If someone already has it open for write access, it will let you know.
If you decide you don't want to modify the part, reload the part and select the read-only option.
Doing this also helped us with our PDM system.
Good luck!

 

[ctopher]

We had a problem with someone opening a copy, it opened as 'read only' without the designer knowing it, he changed it, then saved it. This saved the part as a 'read only' file and was unable to open again, can only be viewed. The only fix was to re-do the part. I suggest if someone is working on a design that uses the part you need to change, have that person exit that file so you can do the changes.
Just my experience.

 

[brengine]

ctopher,
Ouch! I hate doing the same job twice. I've never seen that one. Did you try closing all the files reference the 2 files (i.e. the old and new read-only file), then go to MyComputer and RMB the filename, choose properties and de-select the Read-Only checkmark. The delete/rename the files the way you want them to be?
Just a thought,
Ken

 

[ctopher]

Ken,
Yes I tried that, but it would not work for me. FYI, I use WinXP prof. I was lucky the part was fairly simple and about 1 hour to recreate.

 

[Timelord]

ctopher,

Did you try opening the "read only" and doing a "save as" to another name? The save as copy should be editable. Then you can do a replace where the file was used. Then you can delete the "read only" copy and with the assy open rename the saved as copy to the original name.

Timelord

 

[ctopher]

When I tried to open the read only file, SW did not understand the file type, so it could not open to save as anything else. I tried all kinds of ways to rename, oprn, etc...but no luck. Maybe server problem? Our server has been acting funny lately and is almost full.

 

[JNR]

Here is another suggestion to add to all the excellent repsonses to this thread.

Perhaps it is time to consider acquiring a PDM system? This would truely assist you in handling concurrent design.

Mind you, there would be some overhead involved in selecting and implementing a PDM system, and some (logical and necessary)limitations of its own it would bring to the table with it. However it sounds like you may be at the threshhold where you should be considering this.

3/4 of all the Spam produced goes to Hawaii - shame that's not true of SPAM also.......