VB6 Attach To Process - Com Exposed VBA

I ve been given a VBA spreadsheet which calls functions that are written in VB6 and 'COM' exposed.

Can anyone indicate:

1. How I can find the location of the dll / binary that VBA actually calls in the COMP calls?
2. How I can attach a deb开发者_StackOverflow中文版ugger to VB and get hit when the function os called.

I come from a C sharp background so would really appreciate help here

EDIT: I have the source code and have found the references from Excel - How do I attach a VB6 debugger to Excel and get hit on a breakpoint?

To find out what the library file is, you open the VBA IDE (usually by pressing Alt+F11 in the hosting application) and go to Project->References.
If there's nothing interesting, you want to search the VBA code for calls to CreateObject, which will give you the ProgIDs of the COM objects, which you then can find in the registry.

Lacking the source code, you can debug the VB6 library as you would debug any random application -- by attaching the VS debugger to it.