|
|
Posted by jimshain on 11/26/07 15:08
Since I can call it from a VB program, do you know if I can create a
new DLL using the VB program and use that to access the needed DLL?
If not... If I can call my needed DLL from a C/C++ program, can I
create a new DLL that I could call to get at my needed DLL?
The DLL that I need to call, was bought from a different company, so I
don't have access to the code.
Thanks alot!
Jim
On Nov 24, 9:52 am, "Dan Guzman" <guzma...@nospam-
online.sbcglobal.net> wrote:
> > The DLL was written in Cobol. The "Other-Server" in the Path above is
> > the server that Cobol (and the DLL) is located on.
>
> Not just any DLL can run as a SQL Server extended stored procedure.
> Extended stored procedures are usually written in C/C++, although I've heard
> that some have been written using Delphi. See Creating Extended Stored
> Procedures in the Books Online for details.
>
> Separately, COM DLLs can be invoked using sp_OA* procs.
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "Jim" <jsh...@datamann.com> wrote in message
>
> news:8d9db5fa-a277-400f-9761-7886f9607c55@g21g2000hsh.googlegroups.com...
>
>
>
>
>
> > Hi,
>
> > I have a DLL that I want to run from the Query Analyzer. I tried the
> > following:
>
> > USE master;
> > EXEC sp_addextendedproc BLAH, '\\Other-Server\Path\To\Blah\Blah.dll'
>
> > and I get the error:
>
> > ODBC: Msg 0, Level 16, State 1
> > Cannot load the DLL \\Other-Server\Path\To\Blah\Blah.dll, or one of
> > the DLLs it references. Reason: 126(The specified module could not be
> > found.).
>
> > The DLL was written in Cobol. The "Other-Server" in the Path above is
> > the server that Cobol (and the DLL) is located on.
>
> > I looked at the dependencies for the DLL and it includes (not
> > surprisingly) Cobol Dll's. It should find those on the other server.
>
> > What can I do?
>
> > Thanks!- Hide quoted text -
>
> - Show quoted text -
Navigation:
[Reply to this message]
|