L
Lars Brownies
On http://www.granite.ab.ca/access/corruption/importafterrepair.htm I read:
"Check that MSysCompactErrors hasn't been created or had new entries added.
If it does, then these records document the objects and or data removed as
part of the repair. Make a backup of the repaired file."
Now in a daily maintenance action which is activated when the first user of
that day logs on, the backend of my app gets compacted and repaired.
As a precaution, wouldn't it be a good idea to add a function to the
maintenance routine, that checks for the existance of MSysCompactErrors? Any
thoughts/hints?
Thanks,
Lars
"Check that MSysCompactErrors hasn't been created or had new entries added.
If it does, then these records document the objects and or data removed as
part of the repair. Make a backup of the repaired file."
Now in a daily maintenance action which is activated when the first user of
that day logs on, the backend of my app gets compacted and repaired.
As a precaution, wouldn't it be a good idea to add a function to the
maintenance routine, that checks for the existance of MSysCompactErrors? Any
thoughts/hints?
Thanks,
Lars