>Hi John,
>
>>It works only if I run "after" VFP finished loaded. If I place it in a prg and set as startup program, then I will get error "window 'command' is not defined.
>
>As Fred says, the command window should be active by default when VFP is done... However, in case something strange with restoring docked windows is causing the problem, you could launch a timer in the startup program. The timer would attempt to activate the command window. If it succeeded, it would relase it self.
>
>If you don't mind reconfiguring fonts and window positions, you could also rename your FOXUSER.DBF file and start with a fresh one.

Actually, Foxuser is just a table... and getting acquainted with the types of records in it may be worth the while. I have had my share of problems with it, but never had to kill it. I'd just browse it, find the relevant records (where I suspected the error was saved :), and then delete those records. Pack, Set Reso On and voila.

And my life actually changed for the better when I decided to have a separate foxuser for each project - a little "set resource to .\foxuser" in the environment manager script does that, so I have separate MRU lists where entries have nothing to do with other projects.