Vladimir,

On re-reading the VFP7 Help for CREATEOBJECTEX(), I see that you are probably right, and I was mistaken in my assumption that omitting the cIID argument is equivalent to passing an empty string. I must confess that I am not familiar with this early binding stuff, but I'm learning as I go. It doesn't help matters that the VFP7 Help page on "Early (vtable) and Late (IDispatch) Binding" for some unfathomable reason chooses to illustrate the concept with Visual Basic examples!

Anyway, the problem seems to be more serious than I thought, especially since both Tracy and I had no trouble reproducing it, and Tracy was using VFP8 + Win2K SP3. I have no idea how difficult it would be to obtain an actual cIID value from the registry, but this might be a workaround, unless there are still more problems (as you have indicated, unfortunately). This makes me wonder how many people have actually used VFP's early binding option. It's hard to believe that no one else has run into similar problems, unless hardly anyone has tried it.

Mike

>Hello Michael
> last empty string argument according to docs means -early binding
>I did find only 2 xp computers, where this bug does not take place,
>but it always under 1998, and very often under 2000
>What is strange, Doug Hening said in FoxTalk Intelisence works with amembers(,3) and does not produce the error, if after createobjectexe in command window we observe properties and methods of the object
>We scaned events inside error, and detected , it takes place at ddinitiate inside ememebers
>We also detected, that createobjectex function has othe not so obvious problem
>Sometimes it readss wrong library
>Tomorro I will say, why
>Vladimir