That is interesting. I switched to instantiating the control with NEWOBJECT() and subclassed it so now it is vcx-based also. That was the only way I could get around the design-time license message on runtime systems. It still does the same thing in development. Yet if I click on OK and ignore the error, it compiles anyway the 2nd time. Maybe I can trace this down eventually...
Tracy

>Tracy,
>Interesting. It could well be that the animation form is involved when this problem occurs. As I mentioned to you before, I'm not adding the animation control programmatically. I instantiate the class with NEWOBJCECT() and the class itself is VCX-based.
>
>Are you able to reproduce this problem? I cannot. It only happens occasionally, but when it happens I have to quit VFP.
>
>>I just started having this problem recently in development mode only. I have not opened the debugger and set any break points. However, I did not have the problem until I added the MS Animation Control programmatically and since then it started happening. A prg calls a form calls a procedure in the same prg which instantiates the animation control. I .null. and then release the animation object before exiting, but still, when I try to rebuild, the .fxp stays open. When I ignore the message and click on build the second time without restarting, it will build it.
>>Don't know if this helps or not in narrowing it down or if it is related for sure or not.
>>Tracy
>>