[AccessD] Version Problem -- Emergency

 <<Any other suggestions?>>

  /decompile on a copy of the MDB.  Then do a compile.

  A fresh MDB would clean it up to.

Jim.
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Thursday, August 30, 2007 10:18 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Version Problem -- Emergency

Hi all,

I developed an MDB in Office 2000 and it runs fine. In Office 2003, however,
immediate problems. "Module not found.". Tools | References is greyed out
until I click the stop button. Then the References lists shows Visual Basic
for Applications, Access 11.0 Object library, OLE Automation and ADO
2.1library. That latter sounded obsolete so I unchecked it, and
selected
instead ADO 2.6 and also DAO 3.6 (which some of the code needs). No joy,
however. Attempt to compile produces the same message, Module Not Found.

I'm going to try creating a new MDB from Access 2003 and importing
everything to see if that fixes it. Any other suggestions?

Arthur
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com