Tezcatlipoca
Registered User.
- Local time
- Today, 19:48
- Joined
- Mar 13, 2003
- Messages
- 246
Right, this is the classic programmer's paradox. Day one, project compiles into an MDE without complaint. Day two, same project refuses to do so.
I have an ongoing project that I'm writing for work. Various features/functions are being tweaked all the time, and everyso often I produce another test version for work, which they tinker with, then let me know what they'd like changed. so far, so good.
After the latest tinkering, though, I suddenly find Access 2003 point blank refuses to turn the project into an MDE file, and I simply can't work out why. The project is not large, the main MDB is barely a meg in size, and there are only three tables in the backend, containing a total of maybe two dozen different fields; hardly excessively complex.
When this started happening, I removed the changes I'd made, and found it still refused to compile the thing. If I go back to the previous version (I obviously keep a history of all my old versions) it compiles fine. The logic, obviously, is that I've done something to cause the MDE to run into problems, but I not only cannot see what, but am familiar with Access enough to know that every change I've made should make no difference to the compiling at all, and, indeed, every function I've added or altered, is already being used elsewhere in the database!
So, after much tearing of hair and searing, I'm utterly stuck with this, and Micro$oft's help simply isn't - well - helplful. Any advice on what commonly causes the MDE compiler to fail would be greatly appreciated.
I have an ongoing project that I'm writing for work. Various features/functions are being tweaked all the time, and everyso often I produce another test version for work, which they tinker with, then let me know what they'd like changed. so far, so good.
After the latest tinkering, though, I suddenly find Access 2003 point blank refuses to turn the project into an MDE file, and I simply can't work out why. The project is not large, the main MDB is barely a meg in size, and there are only three tables in the backend, containing a total of maybe two dozen different fields; hardly excessively complex.
When this started happening, I removed the changes I'd made, and found it still refused to compile the thing. If I go back to the previous version (I obviously keep a history of all my old versions) it compiles fine. The logic, obviously, is that I've done something to cause the MDE to run into problems, but I not only cannot see what, but am familiar with Access enough to know that every change I've made should make no difference to the compiling at all, and, indeed, every function I've added or altered, is already being used elsewhere in the database!
So, after much tearing of hair and searing, I'm utterly stuck with this, and Micro$oft's help simply isn't - well - helplful. Any advice on what commonly causes the MDE compiler to fail would be greatly appreciated.
