>Can anyone translate the comments below? Its on the DBI-TECH.COM website and it discusses a problem where a modal form w/ an activex control calls another form w/ another activex control and that 2nd form's activex control's CLICK method doesnt fire.

>Solution: Fox pro has problem with Active X controls on modal
>forms called from other Active X controls. It also has problem
>with calling non-modal forms from modal ones. Instead of
>calling a modal form from an Active X control, call a command
>button and from the command button call the modal form.

In addition to Sergey's references:

This can happen in reverse also. A click on some active-X may not fire a form controls lostfocus.

I use a method similar to the one the solution suggests. You have a command button on a form with a method in the click event. Inside the activex node's click event, you may have code like this:

this.parent.cmdButton.setfocus && Exit the activex and arrive on button
keyboard '{space}'             && Press the button and fire it's click

It could be a regular command button or a little 1 by 1 with the tabstop off.