Request for corruption. I can't seem to find any bona fide way of corrupting an Access db such that I can then test my resurrection code properly. Anyone got any ideas short of taser-ing my PC?
Ta,
Matt
Printable View
Request for corruption. I can't seem to find any bona fide way of corrupting an Access db such that I can then test my resurrection code properly. Anyone got any ideas short of taser-ing my PC?
Ta,
Matt
A sure fire way to corrupt your database is to let the end user any where near it. This is a fail safe system for testing disaster recovery systems, as the customer is always the biggest disaster.
Other than that, write a simple program that messes the data up. This could be done by putting crap values in the database, or you could read the file into a byte array, and scramble some of the bytes, and write the file back.
from my own experience i have noticed that most
access databases when exposed past their 1G limit
become corrupted.
this is not a constant, but you can try to explode
it to the limit.