Hi There,

Thanks in Advance...

Actually Iam in need to update the data's from variety of users from variety of locations...

For that before we used some softwares to just connect them through telephone line for data


But in VFP we can send by E-Mail, but it's not sending by fast, sometime it's delivering after 2-hours...I don't know the reason...Iam not satisfied ...because, Just I checked as per the yesterday code,

Iam in need to send by fast...and proper manner...

Really I don't know what differences with CDO & SMPTP...etc....

For That Anyone Genius To Help Me Please

Doubts By PARAMU

Re: Little Doubts... E-Mail Sending


Paramu wrote:

Really I don't know what differences with CDO & SMPTP...etc....

This is what we had to say on the subject in Chapter 4 of "MegaFox: 1002 Things You Wanted to Know Abouot Extending VFP":

Sending and receiving e-mail

There are many reasons that we might want to send and receive e-mail from within our applications. Perhaps we need to automate the process of sending an acknowledgement for orders received (whether placed on-line or entered manually). Another common use is to include e-mail as part of an error handler so that we can send detailed information about an error to developers and expedite the debugging process. This chapter shows how to implement this sort of functionality.

What are the options

If we can be certain that Outlook is available on our user¡¯s system, then the most obvious choice is to use Outlook automation. The outlook object model provides a rich interface that can be easily accessed using Visual FoxPro. But not everyone has Outlook, or even uses it if they do. So what can we use besides Outlook automation

There are three basic options from which we can choose. First, we can use Microsoft¡¯s Messaging Application Program Interface, better known as MAPI, to send and receive e-mail from any machine on which a MAPI compliant e-mail client is installed. Note that not all e-mail clients are MAPI compliant, but most of them are. Outlook, Outlook Express, Groupwise, and Eudora are all examples of MAPI compliant e-mail clients. On the other hand, Lotus CC:Mail is not.

Second, we can use Collaboration Data Objects for Windows 2000 to send and receive messages using the SMTP protocol.

Third, we could opt for a third party tool which provides a simple interface to e-mail handling. There are many such tools on the market, but for ease of integration with VFP we would suggest looking first at the shareware ¡®wwipstuff¡¯ classes which provide, among other things, support for the SMTP protocol. (For more information see the West-Wind Technologies web site at

What is all this alphabet soup anyway

It seems to be a peculiarity of the computer industry that everything must have an obscure name and, if possible, an acronym. E-mail is certainly no exception, a brief look at the available documentation revealed a host of names and acronyms that very quickly became very confusing. We found ¡°Simple MAPI¡±, ¡°Extended MAPI¡±, ¡°OLE Messaging¡±, ¡°Active Messaging¡±, ¡°CDO¡±, ¡°CDONTS¡±, and ¡°SMTP¡± to name but a few. What are they, and do we need to know

What is MAPI

MAPI is a protocol-independent architecture that separates the programming interface used by client applications from the transport mechanisms used by backend messaging services. The acronym is derived from ¡°Messaging Application Program Interface¡±. It is implemented as a set of functions that can be used to add messaging functionality to Microsoft Windows based applications. The term ¡°Extended MAPI¡± refers to the full function library and gives the developer complete control over the messaging system on the client computer.¡°Simple MAPI¡± is a subset of extended MAPI. It is limited to twelve functions that provide the ability to send and receive messages. The Microsoft MAPI Control library (MSMAPI32.OCX) that ships with Visual FoxPro is an implementation of Simple MAPI.

One important limitation is that MAPI, whether Simple or Extended, supports only plain text messages. If you want, or need, support for HTML in e-mail then you cannot use MAPI. Note; it is important to distinguish between MAPI, which is an application used to access the e-mail client and SMTP, which is a protocol used to send e-mail over the internet.

In order to use MAPI, a MAPI compliant e-mail client must be installed on the local machine and MAPI simply uses whatever application is defined as the default[SPD1] . To find out which client is set as the default (in situations where multiple e-mail clients are installed) just open Internet Explorer and select Internet Options under the Tools menu. The programs tab tells you which e-mail client is set as the default.

One of the consequences of this approach is that sending a message through MAPI automatically posts a copy to the Sent Items folder, just as if the message had been sent interactively. This does not happen when you access messaging services directly.

What is CDO

Collaboration Data Objects (CDO) is, at the time of writing, the current name for what was originally called ¡°OLE Messaging¡±, and later re-named to ¡°Active Messaging¡±. (It¡¯s not surprising that people get confused is it ) CDO comes in three forms in two versions:

¡¤ Version 1.2 exists in two forms. The first form, implemented in CDO.DLL, provides MAPI based functionality and so is limited to plain text messages. It does not actually implement the entire functionality of Extended MAPI, but provides greater functionality than Simple MAPI. The second form, implemented in CDONTS.DLL, is SMTP based and allows messages to contain HTML.

¡¤ CDO Version 2.0, (also known as ¡°CDOSYS¡±) provides an object model for the development of messaging applications under Windows 2000. It is based on the Simple Mail Transfer Protocol (SMTP) and Network News Transfer Protocol (NNTP) standards and is available as a system component on Microsoft Windows 2000 Server installations. (There is also a special version of CDO Version 2.0, which is only installed with Microsoft Exchange Server 2000, and is known as ¡°CDOEX¡±)

What is SMTP

Simple Mail Transfer Protocol (SMTP) is a core Internet Protocol used to transfer e-mail between the originator and the recipient. This protocol uses the structure of the e-mail address to determine whether the components of the message (subject line, content, attachments and so on) can be delivered. The process is initiated when the originator¡¯s e-mail application posts a message to its designated outgoing SMTP server.

The server extracts the domain name of the recipient¡¯s e-mail address (this is the part of the address after the ¡°@¡±) and uses it to establish communication with the Domain Name Server (DNS). The DNS then looks up, and returns, the host name of its designated incoming SMTP mail server.

If all of this works properly, the originating server then establishes a direct connection to the receiving server, using Transmission Control Protocol/Internet Protocol (TCP/IP) Port 25. The originating server passes the user name (the part of the e-mail address before the ¡°@¡±) to the receiving server. If that name matches one of the receiving server¡¯s authorized user accounts, the e-mail message is transferred to await the recipient collecting their mail through whatever client program they are using.


Re: Little Doubts... E-Mail Sending



ThankYou Very Much For Your Kindness.....

I will be Thankful to the following greats...


Whenever I asked doubts, they are all did their very good service....

Now a days even me also changed, If anyone ask me a doubt means Iam also doing with willingness... Because of those above greats....