Bernard,

If there is a TextToSpeech.TextToSpeech you should use that instead, it will map to the the current version. Take the CLSID subkey and look for that CLSID and it'll have the dll mapping as one of it's subkeys.


>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