Sorry for the delayed response.
SerranoG is correct about the compile. Another problem could be that your database is corrupt.
Another way to explain how to check the compile problem is for you to go to the Visual Basic Editor and select the menu option: Debug | Compile. If the compiler finds errors, you'll need to fix those and save your changes.
A quick way to determine if your database is corrupt is to Compact and Repair the database. I recommend that you make a backup of your database before you try this. This method does not guarantee that your database is not corrupt. It will only be an indication that it is.
If your database is corrupt, the simplest way to fix this is to create a new database and import all the objects from your database. When you create the empty database, be sure that it is Access 2002-2003 format before you begin importing objects. You can default the format for new databases by selecting "Tools | Options...". Go to the "Advanced" tab and select "Access 2002-2003"
for the "Default File Format".
If you find you still have problems creating an MDE from this new database, you may have one object that is corrupt beyond repair by this import technique. To find that object you'll need to create another new database and import objects, more or less, one at a time until you find the one that causes the compile to fail. Usually the problem will be in a form or report.
I hope these ideas help. If not, perhaps you could describe more about the things you have tried.
Randall J Weers
Membership Vice President
Pacific NorthWest Access Developers Group