Richard,
It boggles my mind as well. The only thing I can figure out is that the debugger is caught in the Oforms object - I keep running into a 'Read Events' command in the debugger. However, I haven't found any problems with the 'do form' mode of calling a form - all the VMF substrate is still available.

And for a single debugging session it's workable - afterwards just go back to the 'standard' call.

Barbara


>Well, that appears to be my problem . . . but then what's going on. Shouldn't the debugger have knowledge of all that is taking place inside the current session? Most forms I can test and debug using the VM "standalone" features so this is not a mountain, but there are times when a form has so many uses of other framework objects that it is impractical to run as standalone. I guess I'll have to try your idea of calling the forms outside the scope of VM.
>
>Thanks for your quick reply.
>
>Dick