Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 172
  • Last Modified:

uncover hidden objects

I have inherited several old MS Access databases (.mdb) and am in the process of converting them to .accdb.  In addition, I am organizing the databases and extract 'common data' and moving them to a single database that will be linked to the other databases.  This will allow us to keep data current and limit who has access to updating the data.

In the process of creating the new .accdb database -- and copying all of the object in from the .mdb version - I noticed that there was a module and form that were brought over that were not visible in the old .mdb database.  I tried re-compiling the module in the new .accdb - and I get an error msg (see attached) indicating 'User-defined type not defined'.  When I go back to the old .mdb database, I don't even see this module listed and the form is open in design mode.  There is no documentation for the old .mdb database - so I am trying to determine what this 'hidden' module is doing.

Any ideas how to find this module in the old .mdb database?  Any ideas on how to determine what it is doing?

Could there be an external executable that calls this module?

Thanks for the help,
je
C---MS-Access-Database-Consolidation-Err
0
Jeanne Elmuccio
Asked:
Jeanne Elmuccio
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
I can't open your attachment because I don't know what it is.

 As for the error, you'll need not only the code, but the References as well.

 In the old DB, open VBA and look at tools/references.  Those will need to be either:

1. Duplicated in the new DB
2. Replaced with a later version.
3. The code in question that uses the reference be replaced with something else.
4. The code in question that uses the reference be discarded if no longer needed.

Jim.
0
 
Jeanne ElmuccioAuthor Commented:
It seems to work fine even when the code is not compiled.  I tried creating a fake module in the old .mdb database to look at the references -- and got the same compile error.  So I think I'll just leave it as is for now.

Thanks for pointing me to the references.
je
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now