Hi,
I seem to be gettting know where fast with the server support company and my request to have them stop users from being able to delete files, or drag / drop folders all over the place as some unknown users are corrupting one of our network shares.
They told be that removing delete permissions would accomplish this, however, once implemented no-one could save anything created in my applications.
This is apparently down to MS using a temp file which cannot be deleted when saving files.
I was told by the support company that if I re-wrote my code so it created any documents on a location the user has full access to then copy the document to the network share this would work and after two days refactoring all our apps, indeed it does!
However, now when the user opens an exisitng document on the network share and makes any changes, they now cannot save the changes, yet the server support company told me they would be able to?
What do I need to tell them to do so I can have this network share locked down so no one can delete or move folders, but are able to edit existing documents and then save their changes?
I assume this is down to once again the temporary file cannot be deleted when trying to save the changes, so is it possible to tell their MS Office to use a particular location for the temp file where they do have delete permissions?
Or are there folder permissions that will give me what I need?
Thanks,
1DMF
"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Dance Music Downloads
I seem to be gettting know where fast with the server support company and my request to have them stop users from being able to delete files, or drag / drop folders all over the place as some unknown users are corrupting one of our network shares.
They told be that removing delete permissions would accomplish this, however, once implemented no-one could save anything created in my applications.
This is apparently down to MS using a temp file which cannot be deleted when saving files.
I was told by the support company that if I re-wrote my code so it created any documents on a location the user has full access to then copy the document to the network share this would work and after two days refactoring all our apps, indeed it does!
However, now when the user opens an exisitng document on the network share and makes any changes, they now cannot save the changes, yet the server support company told me they would be able to?
What do I need to tell them to do so I can have this network share locked down so no one can delete or move folders, but are able to edit existing documents and then save their changes?
I assume this is down to once again the temporary file cannot be deleted when trying to save the changes, so is it possible to tell their MS Office to use a particular location for the temp file where they do have delete permissions?
Or are there folder permissions that will give me what I need?
Thanks,
1DMF
"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Dance Music Downloads