>I tried all. I didn't wright but first command was to specify port. I also tried ATDT 123123 but without success.
>
>I'll try with documentation but what is going on when I install program on a client side with different modems? Does have I wright procedure for every type of a modem? It's poor solution isn't it?

MSCOMM is not designed as a general modem-based interface - it's a low-level comm port handler, with no concept of a modem, dialing, connecting, etc. You might want to investigate using TAPI, either via the API or through one of several commercial third-party TAPI ActiveX controls. TAPI does understand the modem issues, it works with the current modem configuration information detailed in the registry, including dialing prefixes, area code handling and the like, and as a result, directly addresses the issue of different modem behaviors. While TAPI controls don't ship with VFP, the API services work just fine (your end-user must properly install their modem under Windows, including the TAPI drivers, but doing this also avoids your app having to make adjustments based on their install, and also will handle safely running multiple routines working with the modem - eg fax software, remote control products, internet connections via dial-up networking, that might compete for teh modem, or demanding different initialization from the modem function, or that might otherwise interfere with your app's modem use.

Using the correct API should make your work easier, but does require the user to set up their system properly, where MSCOMM could let you work where the system isn't properly configured for TAPI. OTOH, TAPI offers a common configuration routine, hardware independence and improved coexistance with apps also using the modem, in a standard fashion native to Windows.