vault files being saved over? 2

[DHALE1]

recently we had a problem with files from a protected directory being saved over. We are running windows 2000 and sw2003, and have no pdm system. The problem occured when a file was opened from the protected directory (s:/sw/vault) and was saved-as copy to another directory(s:/sw/work). The drafter did not close the file and goto the copy(in s:/sw/work), so they were still working in the protected directory(s:/sw/vault). When they went to save the file, it saved to the protected directory (s:/sw/vault). When we looked closer, if we did a save-as it would stop you and give you the proper "access is denied" statement for that directory(s:/sw/vault). However, if we did a quick save(or plain save) it would write over the file in the protected directory(s:/sw/vault). we did a test with a word document in the same directory, and it inherited the read only status from the directory (s:/sw/vault) as it should. Our next step was to manually goto properties (in windows explorer) of the files in the vault directory and set them to read only. This worked for the existing files, but any new solidworks parts we put in had the same problem of being able to save over them. We had a solidworks guy in here and he had never seen this before. Has anyone else run across this problem?

 

[JNR]

1. You have no PDM system but are speaking PDM lingo. Please describe your set-up to control files.

2. "Quick save"?

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

 

[DHALE1]

1. We have a document control specialist that moves the solidworks drawings, models, and assemblies in and out of the vault. I guess you could call him our pdm system. What I call the vault is just a directory with read only permissions for everyone except the document control specialist and system administrator. We will eventually get a pdm system, but we are new to solidworks and are currently going thru an SAP implimentation.

2. "Quick save" I mean the save icon or "save"

 

[Arlin]

Sounds more like a server or server permissions problem to me. I don't know how this could possibly be a SWX issue.

If you have your file permissions properly set on the server, SWX has no choice but to obey those rules. It is the server allowing or disallowing writes, not the client (SWX) program.

I would double check how you have your permissions set up and defined. You should be setting these permissions on the serer, not on each user's computer.

 

[DHALE1]

Ok, but how come other windows application don't have the same problem (ie word, excel). We tested these files in the same directory and did nothing extra to them. They behaved as they should with the read only directory. This took us completly by surprise, and we have gone over all settings on the server. We have a system administrator and an IS department doing the settings on the server. If it wasn't for the word file I would agree with you.

 

[Arlin]

Yes, I fully understand your thoughts. The Word/Excel thing is interesting/confusing.

What is your server OS? Has your VAR followed up with SWX? Have you tried Microsoft Tech support?

Perhaps you have SWX setup to run as administrator. I am no network/IT expert, but I think it is possible to run a program in 'administrator mode' giving that program administrator rights.

 

[J-C]

Here's a possible problem.

Both your Vault and Inwork are on the same drive mapping "s" in this case. You set permissions on the "vault" so that everyone there has read-only access. Permissions in the "work" folder has write access for everyone.

What happens is that when your users "copy" files to the work folder, these copies pickup up the permissions of the "Work" folder. Just what you want. However, when your document control guy "moves" them back to the vault, those individual files still have write permissions on them.

What your doc control guy needs to do, is "copy" them back to the vault instead of "moving" them. Then delete the "work" copy afterwards.

This is just how windows functions, moving files across the same drive doesn't change the permissions of those files, but copied file inherit the permissions of the folder they are copied to.


Jason Capriotti
ThyssenKrupp Elevator

 

[DHALE1]

Thanks Gildashard

Thats exactly what it was.