>>I'd be more inclined to write for FoxTalk or CoDe; I'm not much of a writer, ...
>
>Yeah, right! Next thing you'll be trying to get me to believe is that you know very little about Win32/64. Didn't you mention to me that you had done some technical writing in the past?
>

What? Me have a clue about what goes on under the hood? Couldn't be - there's a whole crew who don't think I even know the difference between preemptive and cooperative multitasking...and I wouldn't want to disappoint them with a dose of reality. Not worth the effort to edumacate them about such things. They're happy as clams now with their perceptions of the way the world works and I seem to get bogged down in basic theory, and haven't their academic credentials to hide behind.

Then again, I might have a clue or three...and someone might get a kick out of seeing what the API can do.

>At any rate, anything that I saw in print with your name on it, I'd be sure to read.

Running out of things to line the bottom of the birdcage, George? Maybe I can throw something together on a better ShellExecute() - people are beginning to ask the obvious question about a launch doc via the the API and wait on termination to proceed, and I've got the SHELLEXECUTEINFO structure down pretty well, enough to be looking at an updated API_APPRUN with LaunchDoc() and LaunchDocAndWait() in the near future. With Doug Hennig's recent plug for the current API_APPRUN and circulation of it with the May FoxTalk, maybe it's time to write up something for publication.