I'm sorry Phil. I wish I knew the answer but I've not seen this behavior before. It does sound to be a quirk related to that specific machine but that's not much help since you develop on that machine. Might be some corruption in the OS itself, a corrupted DLL or something.

Since this thread has been alive for several days now with no one else contributing, as I mentioned, you might want to post the info directly to Ed R, G. Tasker, and/or D. Frankenbach. If they've seen the thread and just don't know what it might be, no harm done, but if they haven't seen it, they might be able to give further direction.

Of course, in a worst case scenario if you get no answers and RegClean doesn't work, Rod Paddock's favorite expression is, "FDISK is your friend ..." :-)


>
>This is really getting on my nerves - so if any of the 10**12 guys want to jump in, feel free.
>
>The cause is any use of the run command. Once it executes, I can't use anything that calls a std WIN File Open dialog. This includes File>Open, Program>Do, getfile() and locfile(). No other running programs are affected and closing VFP and reopening it clears the problem.
>
>I again uninstalled VS, did all the usual housekeeping and installed it - but this time to a different drive on the same machine. No difference (growl).
>
>Just thought I'd make one more plea before getting out the registry machete...LOL.
>
>Thanks,