I've noticed what seems to be weird behavior in Win Vista with regards to how it handles dbf tables data. It seems that within my app folder, Vista is maintaining two separate copies of any dbf file - one that stores data from an ordinary user (even a non-top "Adminstrator"), and another that stores data entered by the top administrator.
If I uninstall the app (I use Inno Setup as my installer/uninstaller), and then use the command prompt to look at the hard drive and check if everything has been removed, I see that everything is gone that should be gone. This is true whether I use the command prompt as the ordinary user, or as the top Administrator - I see the same absence of the files.
Then I reinstall the app (again with Inno), and when the app is launched, the old dbf data is still there!
If I then use the cmd prompt and dbu (modified for dbfcdx) to look at the dbf file - as an ordinary user - then I see the old data. If I use dbu as the top administrator, the file is there but empty.
When I do an uninstall followed by a reinstall, I want the data files to be fresh and empty, and that's not happening. (Incidentally, in my Inno Setup script, each file is specified as "Permission: everyone-modify" which should allow them to be erased by the uninstaller.)
Obviously, Vista and its permissions regime is doing something here with DBF files much different than XP, that I don't understand. Can anyone offer an insight into what is happening here?
- Roger