Hey David

Your information re looking in the registry is almost what I was looking for. I examine my registry and I find this entry:

TextToSpeech.TextToSpeech.1

I know this can be used like so
oSp = CREATEOBJECT("TextToSpeech.TextToSpeech.1")
and this creates an instance of the Txt2Speech and I can carry on from there.

But the registry entry does not give any indication of the File name (c:\windows\speech\vtext.dll). Also when I use VFP's Object browser, it appears in the list as "Microsoft Voice Text" and on opening it in the browser it appears as "HTTSLib"!!!!! with a class called "TextToSpeech"

I was wondering if there was any way to connect the 3 especially when the connection is not readily apparent or if I just want to experiment with a COM server I find installed on my computer to see what makes it tick.


Registry: "TextToSpeech.TextToSpeech.1"
COM Tab: "Microsoft Voice Text"
Obj Browser: HTTSLib" which displays the file name vtext.dll

Any ideas?

Thank you for your help re the registry though.

>Bernard,
>
>Yes, select OLEContainer from the controls toolbar, drop it on a form then pick the control, then look at the result OLEClass. But you are right that's only going to do visual controls. CDP doesn't work that way.
>
>You can also browse the registry. They all exist as entries under the HKEY_CLASSES_ROOT item. Skip past all of the file extension entries and there you'll find the COM objects.
>
>As far as finding out the CDO.Message is in fact what you want to use is only going to come from the CDO documentation. There is a Wiki article that lists some of the more popular automation objects.
>
>>By "Drop one of them on a form" do you mean add it as an OLE using the OLE container or just use file manager to drag and drop?
>>
>>Also I always thought that only ACTIVEX (OCX) COM's could be added this way.
>>
>>For instance, will this work with the CDO object I mentioned in my post?