Marvin,
I think I agree with Craig, "Under 2.x there is no way to totally hide the screen. The FPW SCREEN will appear."

What I have is an exe I wrote in 2.6a, it's called BlackBox.exe
Ultimately it will be call from within another program, probably written in VB.
so it'll be:
vb-code
vb-code
vb-code
=BlackBox("TestFile.IN")
vb-code
vb-code
vb-code

I didn't want the BlackBox to do ANY Screen I/O but apparently I can't stop it from opening that one main window.

I guess they will have to live with it until they show us their stuff and convince us of a business reason to create an update that won't blink the screen.

Since there is no visible UI we could have done it in AWK or something...but the original app was/is in Fox 2.6 so this was the fastest way to make our blackbox...and the boss didn't want to disclose the code as we would have to in a language like awk....May be I'll redo it in VFP or Pascal or C or....After they show us their stuff and convince us of a business reason to create an update that won't blink the screen.

Thank you to everyone who tried to help!

Rick
-------------------
>>I've got a program (in 2.6a) that reads a file, processes the contents, creates a file with the results, and quits.
>>
>>It works fine as is...but I have no need for any screen I/O.
>>
>>Is there anyway to have the program do it's stuff without it first creating a "window" to run in? This program may need to run a hundred times a day and I'd rather it not be opening and closing a useless window all day long...that's gotta slow it down some too...
>>
>>Any ideas?
>>
>>Rick Liebespach
>
>I'm not sure if this is what you're looking for or not, but start with the -t switch i.e. c:\fpw26\foxprow.exe -t (program name).