XPost: comp.lang.basic.visual   
   From: mynamehere@comcast.net   
      
   "Otie"  wrote in message   
   news:SpmdnWAtw42VJ7HZnZ2dnUVZ_s2dnZ2d@adelphia.com...   
   >>> What Rick asked was data being moved due to defrag not delete or   
   > reinstall.   
   >   
   > No, not defrag.   
   >   
   >>> For the defrag, that gets tricky since you will need to get the file   
   > alocation table info.   
   >   
   > I think that's what I want. How do I access the FAT info? The system has to   
   do   
   > it in order to find files in the first place. I just don't know if VB can do   
   > it.   
   >   
      
   The point about defrag is that users who run defrag on their disk will be   
   moving   
   your file around on the disk, so you can't rely on it's physical location   
   staying constant.   
      
   VB can call any Windows API, so just about anything is possible in VB if you   
   are   
   willing to chase it down.   
      
   But where are you planning to store the information about the file's original   
   physical location? In the registry? What if the registry entry gets deleted,   
   say   
   by a good registry cleaner program after uninstalling the program? Or maybe in   
   another file that can also be deleted?   
      
   Are you prepared to deal with network drives, both mapped and shared; with   
   backup and restore programs; with anti-virus programs that may move a file in   
   the course of removing a virus; etc., etc. This approach to software security   
   has been tried before, and found to be lacking...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)