Creating MDE Database From Access 97

[Chad Chenoweth]

I'm having a problem creating an MDE database from Access 97. I keep
getting an error saying "There was an error loading an ActiveX Ccontrol on
one of your forms or reports." When I go to Debug --> Compile, it give me
the save error, but won't show me which form or report it is on. I've
looked through the forms and reports and can't find an ActiveX control
missing. I've also looked at my references and don't see any missing
references. How can I figure out which ActiveX control is missing?

Thanks,

-- Chad

 

[Allen Browne]

Chad, chances are this is a partial corruption.

1. Make a copy of the MDB file while Access is not running.

2. Open the database again. From the Tools menu, choose Database Utilities.
Compact. Repair. Compact again. This gets rid of any spurious stuff.

3. Remove any references you do not need. (Typically, you need only Access,
VBA, and DAO.)

4. Close Access, and decompile by entering something like this at the
command prompt (all one line, and include the spaces):
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\My Documents\MyDatabase.mdb"

5. Open the database, and compact again.

Try the compile. If it works now, you should be able to create the MDE.

Post back if that does not solve the problem.

 

[Chad Chenoweth]

Allen,

I followed your instructions without any problem. I was able to complie and
save all modules with no errors. However, when I went to make the MDE, I
get the same error: "There was an error loading an ActiveX control on one of
your fomrs or reports." This is very wierd.

I was able to make this MDE before without any problem. I just got a new
machine at work and tried to make this database, that is when everything
started to go funky. I wonder if it could be an issue with the way they
(the help desk) installed the software on my machine (I have Office versions
for 97, 2000, and XP all installed on this machine). I'll try installing
just office 97 on our test machine and see if that works.

Let me know if you have any other ideas.

Thanks,

-- Chad

 

[Allen Browne]

If it is not a corruption, it's probably a bad reference - esp. as you have
mulitple versions installed.

What references do you have? (Tools | References from the code window).
For example, try unchecking the Microsoft DAO 3.51 reference.
Close Access.
Open a command prompt, and re-register the library, with something like
this:
regsvr32 c:\windows\system32\msjet35.dll
Open your database again, and check the DAO 3.51 reference again.

 

[Chad Chenoweth]

Well, it didn't work on the other machine of ours. I went back to an older
version and everything worked fine. Somehow the database must have gotten
corrupted and no longer let me make an MDE of it.