More likely it was the drivers doing it than VB6 itself... but yes, the users shouldn't be fiddling about with the DB like that... and if they are, that's like breaking the seal and voiding the warranty.

-tg