5

I'm looking to create a COM object in a VBA macro and then pass it to a Delphi DLL (D2009). What should my procedure declaration in Delphi look like?

Background: I'm expecting (hoping) the VBA macro to: create the COM object, invoke the Delphi DLL, pass the COM object to the Delphi DLL procedure, stay alive until the Delphi DLL closes itself (the DLL will have embedded forms for the user to interact with).

I think I'll need to create a callback function to let the VBA macro know that I'm done so it can tidy up but I'll work on that independently of this question.

UPDATE More specifically: What should the exported function declaration be for the Delphi DLL.

1 Answers1

8

you have to pass ADO Connection interface link _Connection to delphi procedure then create TADOConnection instance and replace ConnectionObject with new interface link

library Project1;
uses ADODB;

{$R *.res}

    procedure SetConnection(aDBConnection : _Connection);  stdcall;
    var connect : TADOConnection;
    begin
        connect := TADOConnection.Create(nil);
        try
            connect.ConnectionObject := aDBConnection;
            //here you can use your connection
        finally
            connect.Free();
        end;
    end;


exports SetConnection name 'SetDBConnection';

begin
end.

it is better to use stdcall calling convention. using export keyword setConnection proc is available from uotside with SetDBConnection name , so you can LoadLibrary and getProcAddress to find its entry point (really I don't know VBA so I can't say how to load library using it)

teran
  • 3,214
  • 1
  • 21
  • 30
  • Thank you for that - it will be helpful for the next stage. I added to my original question to clarify that I'm looking for the **exports** declaration. –  Feb 24 '12 at 21:28
  • 1
    No need for `LoadLibrary`/`GetProcAddress` in VBA. You would use a `Declare`. But `stdcall` is essential since that's all VBA knows. – David Heffernan Feb 24 '12 at 21:47