Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Visual Basic and DevLink.DLL 1

Status
Not open for further replies.

SeeThru

IS-IT--Management
May 2, 2002
585
GB
Hi All

I'm trying to get visual basic to use TAPI functions for inbound and outbound - just basic stuff like CallerID and CalledID, as well as dial and answer for a single device.

Development environment in Access97 on Win98 and higher- I know, old school, but M$ costs too much....

I've made some progress using third party TAPI development tools, but they cost and are sometimes rather unhelpful in hiding some of the functions.

Is devlink usable at all by VB? - I'v tried to import the references but it just gives a generic 'Cant add reference' error. All the examples are C++ - I'm hoping there are more options as I'm rubbish at C....
 
devlink.dll is not a COM based dll, so setting the reference in VB won't work.

You will need to open the delink header (devlink.h) and convert the c++ function definitions into VB declares

Its a bit old but the process holds true

]C declarations to VB

Good luck!

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
Besides that, VB for applications is a light version of the VB programming suite.
I think you cannot use the system API calls from VB for applications as you can do from the full VB version.
I have developed my own TAPI program with VB6 and can access all TAPI calls wich i could not do with VB for applications in MS Excel 2000.
If you search on the internet you can find some good and free source code for programming TAPI in VB without the need of the devlink dll.
 
API calls can be made from VBA

However, having looked at this a bit more since last night, I would probably write a COM wrapper around the DevLink dll. Whilst it is possible to use callbacks in VB it isn't a particularily easy...

Likewise, threading may become an issue and VB (or VBA) doesn't handle multithreading (easily or robustly)

I'd help further, but I don't have a CTI pro licence so I can't run any code against a live system

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 

Thanks for the suggestions to Matt and Intrigrant - at least it gives me another option to work with.

There are a couple of commercially writen com wrappers that I have been experimenting with, but at least this will give me the opportunity to try something more direct.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top