CompuServe Messages

Art, This problem was only recently brought to my attention… I think I know _what_ is happening, but am trying to gather a bit more info on it. Some modems have (as part of the extended result codes) a 'RINGING' result is this what yours has? Some modems also let you select the 'extent' of the extended result codes <grin>, is there an 'ATX2' or similar that would set your modem to give you the 'BUSY' but not the 'RINGING' ? Now to the problem… _if_ you are getting the 'RINGING' result, Access! doesn't have any provision for it and defaults to thinking that the call failed for some reason so it will try to dial again (which, in effect, hangs up your modem just as you maybe getting connected). There are a few things that you might try (none of which are pretty, just work-arounds)… 1) if your modem does _not_ echo the 'ATDT1234567' back to you when you dial, then you could NewZap the "AT" in Access! (where I ignore the number being echoed back) and change it to "RI". (If you think this way will work, I can give you more details in the conference or something). 2) if the number you are dialing normally connects on the first ring, you might get away with a short delay after the number… so that the redialer doesn't see the "RINGING" until after you are connected. You can add a delay by adding as many '\w' to the end of your number as you can fit (Access! will process the '\w' as a "wait for x seconds" and you can define 'x' using (of all things) the macro keys… see Access!me for details). There might be a few other work-arounds, or you might just wait until I release the next version… it will have some provision for other "to be ignored " codes. Sorry for the inconvieniance, – Keith