I don't have a high level of experience with this, but I do know that you start down a rocky road when trying to debug VFP compiled COM components. There are at least things that you must do. 1) Ensure that there is no VFP code that can require user keyboard or mouse input directly, such as a messagebox or error routine that expects a user input, OK button, for example. 2) Just about the only way to debug is to start putting coded messages in your code an output them to a text file so you can eventually determine where your program is locking up. For example...

IF FILE('DEBUG.TXT')
=strtofile('Opening table xxx'+CHR(13),'comdebug.txt')
ENDIF

USE XXX

good luck,
Larry

>Hi!
>i have duplicate class olepublic with the same name, thanks Larry
>
>now, well, when i dev a COM work fine in the fox environment but when i use out of the environment (C++) i obtain the task "open" in the taskbar and stay waiting forever.
>
>you have some tip for that problem?
>
>Regards
>
>Francisco Morosini
>
>
>>On second thought, that may not be such a good idea. I was assuming that you had a duplicate library declared previously in VFP. It may be that the name you are using is the same as a Windows system library. What is the class name?
>>
>>Larry
>>
>>>Hi people, I try to compile an exe with public oleclass, but i obtain this error:
>>>Error OLE code: 0x8002802d: the name already exists in the library
>>>
>>>how i can fix this?
>>>
>>>Best Regards
>>>
>>>Francisco Morosini