Printable View
Is there a way to lock a file without having to actually open the file and maintain a "connection" to it from my VB app? This should then prevent other users from writing/deleting/renaming the file. But I also want to allow only my app to write/delete/rename if need be.
Any help on this would be appreciated.
Hi.
Before someone looks in your problem.
Is the system u use a server?Because if it is, i think it's better to use security to prevent people from using that file.
It will be a "server" application. The problem is I need to allow anyone to access the file directly so security is not the way to do it. I basically need a locking mechanism that is not security related. Basically, I'm trying to create a distributed file application where Server1 and Server2 both have the same files and if User1 on Server1 open File1 for editing, it must somehow lock File1 on Server2 as well, so that User2 would not be able to edit File1 on either Server1 or Server2, until User1 unlocks File1 on Server1 and then my application would send the updated file to Server2, and unlock.
Are these files only used by your application? If so then it sounds like you might be better off just using a database rather than individual files.
Having said that - if you only want the file to be locked whilst someone has it open for editing then why are you trying to avoid having maintaining a 'connection' to the file? Couldn't you just open and lock the file when the user opens the file for editing via your program and then just close/unlock the file when they close that part of your program?
That's the key and sorry I didn't make that clear. These files are application agnostic. They are just simply file shares as visible to the user through Windows Explorer. That's why I need to somehow do this at the file level, not application level, but at the same time, I will have some sort of shell program that monitors the file share, and takes are of the updating and unlocking of the file on the other servers. But for this post, I am only interested in how to lock files at the file/OS level.
Yes but you only want to lock them when users are editing them via your program right?
Set the Read-Only attribute and only give permission to SYSTEM to change that attribute (which you would do in your program)?
I thought about the utilizing the Read-Only attribute, but wasn't sure how to accomplish this and wasn't sure if someone who has access to the file share can be prevented from modifying this attribute. So is it possible that my program (running as a service) on that machine, can modify this attribute, but regular users are prevented from doing so?Quote:
Originally Posted by minitech
No. It can be any application. Notepad, Word, etc. But when that file is opened for editing, my program (running as a service on that machine) must get notified that the program is being opened, and then lock (or set read-only) the same file on all other servers. I'm wondering if it is even possible to accomplish this? Really, I'm trying to build a WAFS (Wide Area File Services) system. I wonder how existing system accomplish this? I don't need to use their application, but somehow when I open a file from a share, the WAFS service knows this and locks the same file located on other shares.Quote:
Originally Posted by chris128
I'm starting to this there must be some trickery involved in a WAFS solution. I know that I can create a shell extension program (I think that's what it's called) and install in Windows Explorer to "mimic" an actual share. So that when the user's navigate to this share, they see a list of what appear to be files, but actually, it is the shell extension (program) generating a list of files from a database, and it manages the actual serving of the files. Do you think that's what's being done? But that means installing something on everyone's desktop...
Nope, I just found out that the WAFS solution that I was comparing to, does NOT install any client software. So somehow, they are able to closely monitor the file system and react to users opening files. They claim to employ "native file locking in real time". So how can I do this??
Set the permissions of the file to SYSTEM - All and Everyone - Read.Quote:
Originally Posted by dbassettt74
Then, you can set attributes like this:
And to remove:Code:Dim fi As New IO.FileInfo("location of file")
fi.Attributes = (fi.Attributes And IO.FileAttributes.ReadOnly)
Code:Dim fi As New IO.FileInfo("location of file")
fi.Attributes = (fi.Attributes And (Not IO.FileAttributes.ReadOnly))
As per my earlier note, I don't think I want to employ this method of using the read only attribute. I want to employ some way of using native file locking.
That's what I'd call "native", it's completely managed by Windows.