Hi!

There are a lof of different versions of the CDO. There are articles about versions and installers that install these objects. Basically, version 1.0 is called ActiveMessaging and available when you install Internet (Microsoft?) mail components. However, this version is unstable and have limited number of features. For example, it do not allow to connect to Exchange server directly, connect only using local profile, that usually is default Outlook profile - this have no advantage over simple use of Outlook. See following link:

http://msdn.microsoft.com/library/techart/cdo_roadmap.htm

We cannot post a sample because it is full featured testing application with sending XML, receiving it using CDO and parsing it. We work now on the installing of the CDO without installing anything else, but seems this is complicated task. MS had their own installer for CDO objects, now it is not available any more from MS site. Seems it was as experiment that they do not support anymore. Now CDO could be installed only using other products as mentioned in the MS article.

>Hi Vlad,
>
>Here in the office we use Windows 95 (don't know, when we'll upgrade). Whould it work?
>
>Will you post your demo form here?
>
>Thanks in advance.
>
>>Hi!
>>
>>CDO 1.21 is available for NT with installation of the Exchange Server 5.5 or Exchange Server 5.5 administration utility. I just finished a demo form with use of these objects and have seen how it works really. It resides in the CDO.DLL.
>>
>>There is also CDONTS library, which I did not managed to get to work.
>>
>>>Thanks Vlad
>>>
>>>This is very intresting but the MSDN website says.
>>>
>>>
>>>The CDO for Windows 2000 COM component (Cdosys.dll) is an integral part of the Microsoft Windows 2000 series of operating systems; your application does not need to install the component. CDO for Windows 2000 does not run on other operating systems such as Microsoft Windows 98.
>>>
>>>This appears to indicate all my remote customers must have
>>>Windows 2000 installed.
>>>
>>>Some of the users running the system will be small independant building contractors ie "one man and his dog outfits" and we have only just got to the point where we can be sure they have internet access and Email access.
>>>
>>>Other users of the sytem will be large corporate builders with Windows NT and firewall issues:(
>>>
>>>Can CDO still help me?
>>>
>>>
>>>Many Thanks for the input:)
>>>
>>>
>>>
>>>
>>>
>>>>Hi!
>>>>
>>>>The answer is CDO! Collaboration Data Objects 1.21 or higher works great. Just read articles about it in MSDN. There is full help for these objects. I tried them and they work great with attachments for both Exchange Server and Outlook folders. More, they're ideal for automated services. We tried Outlook, SMTP and MAPI controls for these purposes too. We forget about MAPI controls so far. SMTP is good for mail sending only, when receiving is still requires something to check for email. Outlook is great but it is unstable and unreliable for automated services (even when working through CDO). We tried it and experiensed several limitations and possibility of user intercations that broke service working in Outlook.
>>>>
>>>>>All comments most gratefully received:)
>>>>>
>>>>>
>>>>>This thread is carried over from the thread
>>>>>Re: Nigel Coates MAPI Class or Outlook class which should I use
>>>>>because Nigel answered the original question.
>>>>>
>>>>>I am hoping to write an application that transfers Zipped DBFs as attachments.
>>>>>
>>>>>The idea behind the application is the my app will pass these DBFs back and forth beween remote locations using the Email system without any involvement in the process required by the user.
>>>>>
>>>>>Ideally the user will remain completly unaware of what is happening. New data will just start to appear in his app every so often.
>>>>>
>>>>>The application would be distrbuted to hundreds of external contractors and they would use it to receive tenders/works orders from ourselves and use it to complete these tenders/works orders and return the information on them to ourselves.
>>>>>
>>>>>The main advantages and disadvantages of the differing methods seem to be as follows.
>>>>>
>>>>>1. SMPT Control
>>>>>
>>>>>Advantages.
>>>>>By using just classes that deal with SMTP the application will be acessible to the widest possible number of users. SMTP classes will not care what email client the user is using because it will be not be using it.
>>>>>SMTP will be around forever just about.
>>>>>
>>>>>Disadvantages
>>>>>Corporate users may not be able to connect to the SMTP server through their firewall. I cant find any stuff on receiving SMTP mail that has a VFP slant.
>>>>>ie I might have to do it all myself:(
>>>>>
>>>>>2. MAPI Control
>>>>>
>>>>>Advantages.
>>>>>Many users will have a MAPI complient Email client but there is chance this may change in the forseable future (Office XP according to our network guys)
>>>>>The users will not require MS Outlook on their PCs
>>>>>
>>>>>Disadvantages
>>>>>There may be a problem in trying to retrieve an attachment when those attachments are stored in MS Exchange rather than on the PC it self. HELP!
>>>>>
>>>>>3. Outlook Control
>>>>>Advantages
>>>>>Using the Outlook control provides access to the Outlook folders so the mail can be deleted after the attachments have been read. This will provide a much tidier solution for the user than MAPI.
>>>>>
>>>>>Disadvantages
>>>>>All the people who use the system must also have MS Outlook on their machine so there are licence issues involved even assuming that they are happy to have Outlook sitting there upsetting their existing mail system:(
>>>>>
>>>>>There are a few of us trying to achieve this in UT at present and a good discussion in this area will open this technique up to many.
>>>>>
>>>>>Thanks
>>>>>
>>>>>Mark