>>
>>Ed, it is a simple point: There are probably many programs out there that would be screwed-up if SCREEN=OFF was placed in the CONFIG.FPW file.
>>
>>Notice the period. I was not placing blame. I was not talking about AUTOEXEC.BAT, etc., etc., etc.. That is the scope of my statement. I think it is true. If you think it is false, just say so.
>>
>
>Right. There are programs that could be screwed by putting a bad CONFIG.FPW in place. Period. There are programs that could be screwed up by putting in a bad AUTOEXEC.BAT, too. Period.

Sure, so why don't we leave it at that?

Oh, I see, there's more...

>
>I don't see CONFIG.FPW as any more evil or dangerous than AUTOEXEC.BAT, and that's where we differ. You're entitled to not use it, and can protect your applications from being hurt by it by including one in the app, or by adding the -C command line switch with no file name, to force VFP to ignore it.
>
>Do not operate power tools or drive farm equipment while stoned on opium.
>
>The Surgeon General has determined that a squirrelly CONFIG.FPW can cause cancer in a VFP app that hasn't planned for it's effects.
>
>Caveat developer.

Haha...let me quote your statement: "I don't see CONFIG.FPW as any more evil or dangerous than AUTOEXEC.BAT, and that's where we differ."

When did I compare CONFIG.FPW's level of danger to AUTOEXEC.BAT's level of danger? Ed, you are assuming things.

Joe