Is there a replacement for this so we don't have to make VBA Object library
references to Utility.MDA?
I have an application that crashes more often than not because of this
Utility.
Thanks for you replies!!
Try this. Place the following at the top of a module (underneath the option
declarations and before any procedure code) :
Declare Function TAPI_Make_Call Lib _
"tapi32.dll" Alias "tapiRequestMakeCall" _
(ByVal stNumber As String, _
ByVal stDummy1 As String, _
ByVal stDummy2 As String, _
ByVal stDummy3 As String) As Long
Then use it like this:
TAPI_Make_Call "123456789", "", "", ""
It's been quite a while since I used this, I have no modem on this machine,
and I'm unable to remember whether it requires a formatted number or not.
Play with it till it works...
http://support.microsoft.com/default.aspx?scid=kb;en-us;148857
Thanks for that. Once a year or so we see a similar request and I've
always wanted to have another solution. However I've been to lazy to
do any searching.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
No problem. Back when I was experimenting with various dialling methods, I
pasted this code into a module and ran it. It worked "right out of the box".
I never ended up using it though, as my client was satisfied with the way
tapiRequestMakeCall behaved.
> Is there a replacement for this so we don't have to make VBA
> Object library references to Utility.MDA?
>
> I have an application that crashes more often than not because of
> this Utility.
Without the reference, call:
Application.Run("Utility.wlib_AutoDial")
I just tested it in A2K3, with no reference. Obviously, you'd pass
it appropriate arguments.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/