I've got a big bunch of code I'm trying to put into stored procedures. I gotta use CaLLS to sub-procedures.

I'm using v7.2 on windows.

But when I try to run procedure that calls another, I get this:

SQL1109N The specified DLL "TRADEIN1.LSH_ACCOUNTINFO" could not be loaded. SQLSTATE=42724

the SQL1109n talks about this:

SQL1109N The specified DLL "<name>" could not be loaded.


Explanation: The DLL (dynamic link library) module specified could not be found.

The command cannot be processed.

User Response: Ensure that the specified file is in a subdirectory identified in the system LIBPATH

Now, I know I dont' have to worrry about the libpath, I've got some kind of scoping problem between my client dev workstation and the server.

Where its running is probably the problem, but what do I do in the Stored Procedure builder to let it know how to find its elbow in the dark?

Thanks,

Kimball