XPost: microsoft.public.vb.general.discussion, microsoft.public.vb   
   From: noway@nospam.ever   
      
   "Don"  wrote in message   
   news:48ce6af9.6715546@news.west.cox.net...   
   > Although this has great possibilites, I'm not sure how confident I   
   > will be using it due to concerns I mentioned previously regarding the   
   > consequences that might result if the program shuts down unexpectedly   
   > and we're left with the original file locked . . .OR would the file   
   > detect that my app has shut down and revert back to being available?   
      
   If there is a crash or your app aborts for any reason then recovery would   
   depend on whether you've saved the state of "user x is editing text y in   
   location z" somewhere.  If you didn't then any changes are lost and if you   
   did you can decide to restart the editing session (maybe asking the user in   
   case it's an endless loop).   
      
   If the user's text editor crashes then you should see it terminate and can   
   take precautions -- maybe check the return value of the editor app and if   
   not 0 then ask the user to confirm that it is OK to update.... maybe compare   
   the before & after versions and if the sizes aren't close ask the user to   
   confirm...  nothing is ever going to be foolproof so it's up to you to   
   decide how many hoops you want to jump through and how many you want to   
   force your users through.   
      
   As soon as you do this you're going to find users editing the text on the   
   originals while your app is not running.  Unless you're encrypting the text   
   and putting it in a difficult-to-find location the users are going to find a   
   way around any restrictions you set.  Even if you do those things somebody   
   probably still will.  *&%^&^%^& users!   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)