Locate OCX/DLL files used in Access app

[Pat]

I've been called in by a client who has a large database app that he want't
to move from location to location.

He wants me to document what additional, custom files may be used in the app.

Unlike VB6, for example, where you know exactly which additional custom OCX
files/or routines inside (possible) custom dll's exist, how can this be
determined in an Access DLL.

I tried to make it into a MDE in the hope than a low-level dependency list
might be created, but the attempt failed and don't want to spend time on that
red herring.

Anyone got any suggestions please?

With thanks in anticipation

 

[Douglas J. Steele]

Look under Tools | References while in the VB Editor to see some of
referenced OCXs or DLLs.

Look for any Declare statements in your VBA code to see whether they point
to specific paths.