Program repairs itself when accessed

[Darryl]

I have installed a proprietary OLEDB provider program on Win98, Win2K,
& XP.

On 98 & Win2k, I can delete the shortcuts & the executables, & still
use the functionality of the OLEDB provider using Visual Basic
programs. These deletions are done for security reasons, so users
can't create their own queries with the OLEDB query wizard.

However, on XP, when I start the VB program, it accesses the OLEDB
provider & the OLEDB provider instantly restores the deleted shortcuts
& the deleted executables before executing the VB program.

Is this "autorepair" part of XP? It doesn't happen on the other OS
versions. Is there anyway to turn it off either for that one program,
or else system-wide?

 

[Yves Leclerc]

If the files/executables are flagged as System files, the XP will restore
them automatically.