This is completely untested. I do not have a computer on hand that has anything attached to any of the serial ports (modems). Note: this uses COM1:. You may want a different communications port, and in any case, you will need to map the COM you do use to the appropriate hardware (if that has not been done already).

The following sets the DOS defaults for COM1: - It would be better to use the Windows device manager to preconfigure the port to the appropriate baud setting to get 56K.

var sh as int

sh = @Shell("mode com1: baud=9600 parity=n data=8 stop=1")
 

var fileNo as int

fileNo = FileOpen("COM1:")
FileWriteLn(fileNo, "+++") // Send command mode
FileWriteLn(fileNo, "ATZ") // Send modem reset
FileWriteLn(fileNo, "ATDT555-555-5555") // Dial the number
// Wait for connection
// Here write the data to the modem
FileWriteLn(fileNo, "+++ATH0") // Hang up.
FileClose(fileNo)
 

The code above assumes that you have a Hayes compatible modem. It also assumes that you are using tone dialing (use ATDP for pulse dialing). It should also use FileReadLn to read back the modem's responses. Hayes modems will usually reply "OK" if a command works and is done.

Quote:


I assumed that you were trying to connect using a modem (not a telephone to another person). If all you are trying to do is dial the phone (not send data), there are a number of third party phone dialers available that can be "shelled" - including one built into windows. In Win2000, it is at c:\Program Files\Windows NT\dialer".

Hey Bob -

As I said before, I'm very surprised that this hasn't become a "routine task" by now. 

In any event, I looked through my Q&Answerman database again and, this time, I found a record dealing with the issue (that I must have overlooked previously).  It had the "original solution" for Q&A 5.0 using the @shell command to a .bat file (I believe those things are still available in Windows XP).  (If you're interested in looking at the Q&Answerman solution [and the article I had written in the April 1996 issue of The Q&Answerman newletter], just search for a keyword of "Dialer."  It should bring up only the correct record).

So, if necessary (and for now at least), I will try playing with a batch file.   For some reason, though, I feel like I am going back into the "dark ages" and can't help but feel that there must be an easier  - more direct - way to do this in a program as sophisticated as Sesame.

http://www.quickanswer.com/dnlds2.htm

contains the Q&A 5.0 tool DIALER.zip to download...

Spencer,

switching the .bat batch file content of:

http://www.quickanswer.com/Dnloads/dialer.zip

from current COM 1 to COM 3 and after treatment by Sesame´s Q&A file translator along with some modifications to link up your customer database content to the dialer, you would then not only own a dialing tool but a phone log book along with a searchable comment field too... ( imagine, just typing the nickname of your girl friend and BINGO, you are almost connected..., and drop a rendezvous-date within the comment lines sequel to the motto: NEVER FORGET - NEVER REGRET..., a meeting with your loved one)

Quote:

Do you have a file called "Com3" sitting in the directory you were in when you ran the above command. I think it is necessary for the com name to be followed by a colon: "Echo ATDT > COM3:" The colon tells DOS that you are using a device, not a file.

Unfortunately, I have still not gotten my phone dialer set up.  I discovered, however, that there must be a very basic problem.

I went to a Command Prompt and typed:

    Echo ATDT >Com3   

which - from everything I've read here in the forum, in the communication link Bob Hansen was kind enough to provide and elsewhere - SHOULD work and I should HEAR a dial tone.  I do NOT hear a dial tone.

Alternatively I added the colon, as suggested and typed:

     Echo ATDT >Com3:

and that did not work.  (I also tried tried it including %1 and with an actual phone number and that made no difference).

I know that the echo command works because when I typed:

     Echo Hello World

I saw Hello World on the screen.

I know that the piping works because when I typed:

    Echo Hello World > LPT1

Hello World printed on my HP Laserjet 5 printer.

I know that the modem itself works because when I use MS Access' built-in phone dialer (WOULDN'T IT BE NICE TO HAVE ONE IN SESAME!!! - hint hint)    the dial-tone works just fine and my call is properly executed.

So, now, I am waiting until I can discuss this with my 'hardware/Windows XP' expert to see whether he has any suggestions.

Walk-To-Fly - I appreciate your suggestion about the Q&A 5.0 phone dialer file; however, I would prefer not having to convert a database from Q&A (which I haven't done yet) and I don't necessarily need the other features (such as reminders which I can handle within Sesame).  Also, I prefer to get the batch file working because then I can make my own choices such as whether I want to provide a command button for each phone number (home, work, etc.) or whether I can handle it by on-focus of the layout element, or a list, etc. etc.  I will certainly keep this software in mind, though and thank you for recommending it.

It is just very frustrating that I was able to do this so easily with Q&A 5.0 as long as nine years ago and am having so much difficulty getting it to work in Sesame (and/or Windows XP).

Finally, in case anyone is interested, when I typed

     mode com3: baud=9600 parity=n data=8 stop=1

this was my on-screen result:

C:\>mode com3: baud=9600 parity=n data=8 stop=1

Status for device COM3:

     Baud            9600
     Parity:            None
     Data Bits:            8
     Stop Bits:            1
     Timeout:            ON
     XON/XOFF:      OFF
     CTS handshaking:      OFF
     DSR handshaking:      OFF
     DSR sensitivity:      OFF
     DTR circuit:      ON
     RTS circuit:      ON

(whatever that means)