I have only worked a little with calling a DLL, so I would like to see if anyone can spot my error. When I try to call one of the DLL functions I get the following message "Function CSTAGE_GET_NUMBER_OF_SCHEMAS does not exist in dynamic link library CSTAGE.DLL".

I'm not sure if the names are case sensitive, the error message displays the function name in all Caps, but the function name is actually "Cstage_get_number_of_schemas". I used a utility to read the DLL to make sure my function existed and to make sure my spelling is correct.

I have placed my dll "CSTAGE.DLL" into my oinsight directory. I created a record in SYSPROCS with the following

CSTAGE

UINT PASCAL CStage_get_number_of_schemas(VOID)

I ran DECLARE_FCNS "DLL_CSTAGE".

I DECLARE FUNCTION CStage_get_number_of_schemas

but when I try to use the function I get the above error message.

Am I missing any steps??? Or any advice as to what I should look at next?

Thanks,

matt

Matt,

I'm not sure if the names are case sensitive, the error message displays the function name in all Caps, but the function name is actually "Cstage_get_number_of_schemas". I used a utility to read the DLL to make sure my function existed and to make sure my spelling is correct.

Names in the *declaration* are case sensitive, though not when you call the function in your basic+ program

I have placed my dll "CSTAGE.DLL" into my oinsight directory. I created a record in SYSPROCS with the following CSTAGE UINT PASCAL CStage_get_number_of_schemas(VOID)

Are you sure about the calling convention? PASCAL was the standard for Win16, STDCALL is the standard for Win32, so try that instead.

The Sprezzatura Group

World leaders in all things RevSoft

I have tried both conventions, and I get the same error. I set it back to STDCALL, ran DECLARE_FCNS, and I am still getting the same message.

Did you log out of OI after you ran declare_fcns? The declare_fcns routine doesn't knock the old DLL stub off the program stack, so you really need to get it refreshed…

The Sprezzatura Group

World leaders in all things RevSoft

Actually, looking at the source for the DLL you may find the calling convention is CDECL rather than STDCALL… so give that one a try :)

The Sprezzatura Group

World leaders in all things RevSoft

That still did not correct the error. How can I confirm I am using the correct calling convention?

So you tried CDECL? What does the CSTAGE DLL documentation say? You're sure it's 32-bit DLL?

Try using the isLib() function to see if it can actually by found and loaded by OI. It may be a dependancy issue - as in CSTAGE.DLL may need other DLL's to be in the path before it can load.

declare function isLib

ok=isLib( "CSTAGE.DLL" )

The Sprezzatura Group

World leaders in all things RevSoft

Islib returns a 1.

The documentations doesn't mention which convention should be used to call the functions. What I do know about the DLL is it is written in C. I have access to the source code, it is public domain, will that answer any questions? In regards to whether the dll is 32-bit I am not 100% certain. I was getting the same errors in a 16-bit account so I moved to a 32-bit account prior to this morning. When I read the header of the DLL the subsystem is Win32GUI.

thanks,

Matt

Any other suggestions, or tips?

thanks,

Matt

This IS the Cancer Staging routines yes?

#ifdef WIN32

  #ifdef CSTAGE_EXPORTS

  #define CSTAGE_API __declspec(dllexport)

  #else

  #define CSTAGE_API __declspec(dllimport)

  #endif

#else

  #define CSTAGE_API

  #define _stdcall

#endif

So it seems to be using CDECL. Can you post your MODIFIED declaration for us to check?

The Sprezzatura Group

World Leaders in all things RevSoft

Yes, the routine is for collaborative staging (cancer related). I have made some progress. I noticed they also had made a DLL specifically for Visual Basic. This DLL functions as a shell around the CSTAGE.DLL. I gave it a try and it seems to be working and I'm using STDCALL to call the functions in the VB dll csdllvb.dll.

But I'm curious why I can use the functions in the CSTAGE.DLL directly. My modified SYSPROCS looks like this for the CSTAGE.DLL

CSTAGE

UINT CDECL CStage_get_number_of_schemas(VOID)

Thanks,

Matt

Sorry I had a typo in the previous post.

I meant to say "I am curious why I "Can't" call functions in the CSTAGE.DLL directly"….

View this thread on the forum...