At some customers we have the problem that the database (mde) is corrupt after using CompactDatabase in VBA.
Instead of CompactDatabase we use the jetcomp.exe tool.
The jetcomp.exe does not support accde.
Is there a tool to repair accde databases?
At some customers we have the problem that the database (mde) is corrupt after using CompactDatabase in VBA.
Instead of CompactDatabase we use the jetcomp.exe tool.
The jetcomp.exe does not support accde.
Is there a tool to repair accde databases?
I have no knowledge of that, but am curious to ask: is the db split? I ask because I would think it rare that the fe (as an mde or accde) should need compact/repair if it has no (or minimal) tables. If it's the be you're referring to, then I don't see a reason to make it an mde or accde. It's not something I have ever considered doing.
If that makes any sense, you might be able to prevent the need for cr rather than fixing a db afterwards. It's often said that a backup copy should always be made just before performing cr.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
I make a copy of my db,
then compact.
It doesnt happen often, very rare, but I had one corrupt upon compact.
NEVERMORE!
Yes the db is split.
The data is in a seperate database.
The data database is at the customer.
We need to compact because the database becomes too big.