Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Tapping into TAPI
Message
De
17/04/2000 07:43:31
 
 
À
17/04/2000 06:51:11
Information générale
Forum:
Visual FoxPro
Catégorie:
Fonctions Windows API
Divers
Thread ID:
00360282
Message ID:
00360291
Vues:
7
>Hi All,
> I have been looking at including being able to dial direct ot of my App.I have seen a few samples but nothing to the extent that I am looking at. I want to learn how to control the TAPI directly but seem to find very little useful 'plain English' articles. I am only reasonably new to FoxPro and havn't had a lot to do with calls to the windows API. The following code is the closest that I have found to what I am looking for but it uses the standard Windows dialer which stays open after the call. I want to be able to control the entire process on my form and include features like poping up a msg if the line is busy, modem in use etc, and auto redial features. I know I want it all , but if its worth doing its worth doing properly. I have
>checked the helpfiles on TAPI but don't understand the parameters that they are looking for. A little 'plain English' help would be much appreciated.
>
>DECLARE LONG tapiRequestMakeCall IN "TAPI32.DLL" ;
> STRING cTel, STRING cApp, STRING cUser, STRING cComment
>lcTel = ALLTRIM(THISFORM.txtPhNo.VALUE)
>lcApp = "empty"
>lcUser = ALLTRIM(THISFORM.txtComName.VALUE)
>lcComment = "empty"
>nErr = tapiRequestMakeCall(lcTel,lcApp, lcUser, lcComment)

Don't use the TAPI API calls unless you're willing to invest a whole lot of time writing low-level API code - you'd be far better off with either the MSCOMM32 ActiveX control, which gives low-level serial port control, or an ActiveX TAPI control.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform