Do you have VS6.0? If yes, install the tools for VS6.0. There's a great Dependent (I'm not sure that's the exact name) tool.

You can load into it any exe, dll, ocx file and see what other dlls/ocxs/etc are needed. Almost obvious, it will not show dlls linked using macros (for ex: DECLARE AFunction IN &lcDLLName) or similar hidden links, because it doesn't run your code, but only looks inside the executable file and extracts all explicit links.

Vlad

>Greetings!
>
>I'm working in a Win95 network environment, but have an VFP5 EXE I want run at scheduled times on an NT server. My launch menu automatically copies the necessary files (vfp500.dll & vfp5enu.dll) for a Win95 environment, which eliminates the need of installing the app on every PC, since the app does not use any extended features.
>
>However, this method won't work on the NT server since it apparently needs a different library file.
>
>Therefore, what library file(s) is/are necessary to run a vanilla EXE on an NT machine?
>
>Thank you!
>
>Michael Reynolds