I am a mechanical engineer doing some small programming for a mining
company.  The programming
involves communication with (3) D/A boards which of course requires the
use of DLL files to communicate
with the boards.

With one of the boards, only a 16-bit DLL file is available, and as a
result, I have been setting up an OLE Server to
"thunk" between 32-bit code and the 16-bit DLL.

The problem I keep having is that during run-time, an error code '53'
(File not Found) error comes up when trying to
access the functions of the DLL.  At first I thought it was an error
with the DECLARE statement, in that I did not have
the file location adequately referenced.  This does not seem to be the
problem.  I also tried accessing the functions of the DLL
with the 16-bit VB4 - and I still get the same error.

As this is a DLL developed by the board supplier does anyone know:

Is it possible that the DLL itself is trying to call another  file and
because this file is not present or not in a correct directory, there is
an error?  Would the same run-time error occur as if it were a mistake
in the DECLARE statement?

I haven't had any other problems with using DLL's otherwise,  any input
would be welcomed as I am stuck.

Try to put it in the windows system directory

A dll is 'nothing less' than an normal EXE, so actually it could start anything it needs.

    I am a mechanical engineer doing some small programming for a mining company.  The programming
    involves communication with (3) D/A boards which of course requires the use of DLL files to communicate
    with the boards.
    With one of the boards, only a 16-bit DLL file is available, and as a result, I have been setting up an OLE Server to
    "thunk" between 32-bit code and the 16-bit DLL.

    The problem I keep having is that during run-time, an error code '53' (File not Found) error comes up when trying to
    access the functions of the DLL.  At first I thought it was an error with the DECLARE statement, in that I did not have
    the file location adequately referenced.  This does not seem to be the problem.  I also tried accessing the functions of the DLL
    with the 16-bit VB4 - and I still get the same error.

    As this is a DLL developed by the board supplier does anyone know:

    Is it possible that the DLL itself is trying to call another  file and because this file is not present or not in a correct directory, there is an error?  Would the same run-time error occur as if it were a mistake in the DECLARE statement?

    I haven't had any other problems with using DLL's otherwise,  any input would be welcomed as I am stuck.