If you try to execute the procedure just by using SQLExecDirect() (prepare and
execute) it can result in this error!. It will work if you do SQLPrepare() and
SQLBindParamter() and then execute.
Regardless of the type of parameters. Check the following,
1.If this can be executed on the server (using CLP)or from stored procedure builder ?.
2.That you are passing the right parameters (Number,TYPE, DATATYPE, etc.)
If you pass the wrong parameters, it can result in this as the server
won't be able to find the library with the right entry point.
3.If you getting this error from ADO (I guess you are, because I see the Microsoft OLE
DB provider message :-), use CreateParameter() of the command object to bind the
parameters to the command object
and then execute it.
Regards,
Ajith
-----Original Message-----
From: Sinha, Amit [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 6:28 PM
To: [EMAIL PROTECTED]
Subject: DB2EUG: SQL1109N
Hi All,
Can someone what am I missing to get this error. We have created the stored
Procedure and given the package execute authority
to user.
Below is the error that I am getting:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[IBM][CLI Driver][DB2/NT] SQL1109N The specified DLL "CreateAdver" 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.
sqlcode: -1109
sqlstate: 42724
What do I need to set ?
Thanks.
Amit
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
