|
|
Posted by jimshain on 11/27/07 14:17
Thanks for the pointers!
Jim
On Nov 26, 5:35 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> (jimsh...@gmail.com) writes:
> > 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.
>
> Yes, you could write one or more extended stored procedures to access
> the DLL. Or implement COM methods.
>
> On SQL 2005, you could to a COM-interop and call it from CLR.
>
> Whatever, it's a bit of work, and and if you have errors in your
> code that causes access violation, you could crash SQL Server.
>
> To get information about writing extended stored procedures, please
> see in Books Online for details. If you have never done it before,
> expect at least 50 hours of development.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|