Daniel,

> Thank you very much for your help.
> The Emulated Command Window I'm trying to create is designed for own support. It's called by a 'Development' menu which is only available
>when the application starts with a special parameter. Like you said, we don't want users mess things up as well. THat's why I can't simply
>use 'Read & Clear Events', anyway It's not a big issue as long as It works for Sql and functions. I think I rarely need to create variables there.

After your post, I looked into the project again, and made some adjustments to let it work in an application with a READ EVENTS trick. I'll test this again, and mail you the result. I'll also update the file in the files section.

> I also check the Visual Foxpro help and know that all variables declared in Foxpro command window are automatically PUBLIC. Maybe that's
>why I got 'Variable .. NOt found' problem in my fake command window.

Yep, this is the reason why I have to execute the commands at the lowest program level. I simply can't ensure that every variable that is created is automaticly scoped to public.

> The Infinite Loop problem, you should be able to duplicate by press Enter key (maybe twice) in your command window. I'm not sure it's related
>to Visual Foxpro version or not. I'm still using Visual Foxpro 5.0a.

I've build it in VFP 6 SP3, but I'll check this for VFP 5.0a.

Thanks....

Walter,

>Thanks,