title: Is filesystemwatcher the right way to monitor a file?
body: <p>I know it’s a general question but I’m just opening this for discussion.  I have to assume someone else must have done similar and I don’t want to do a lot of code to find out my solution wouldn’t work.</p>
  
  <p>Here's what I have.  A user will add a file to the database as an OLE object and associate some attitude to the file - project it's associated to, version etc.  I’m using Access – customer choice not mine!</p>
  
  <p>When they want to edit it, they will need to check it out.  At this stage I want to monitor the file and when they save it, to restore it back to the database.</p>
  
  <p>I'm thinking that file system watcher is my best way - monitor the change and save it back to the database when the change even is triggered and I can gain access to the file.  If it's still opened the application will have it locked so I know that the user isn’t finish.</p>
  
  <p>So in short my question is file system watcher the proper way to approach this?  Anyone suggest anything else?</p>
  
  <p>Thanks,
  Jim</p>