>On my machine, when I bootup or launch of VFP 6.0, TALK gets SET ON.
>
>I have setup file that runs as the last command in Config.fpw. I can put "SET TALK OFF"
>as the command in Config.fps RIGHT BEFORE calling the setup file and I can put "SET TALK OFF"
>as the LAST statement in the setup file, but when the program returns to Config.fpw,
>TALK gets SET ON.
>
>Even with no setup file called and "SET TALK OFF" as the last command the Config.fpw,
>TALK still gets SET ON.
>
>I can always issue "SET TALK OFF" from the command window, but why should I have to?
>Where's my oversight?
>
>TIA
>
>F. Bennett Swenson

I suspect the forms you are using in your application have their own private data session.

the SET TALK command is an example of a Visual Foxpro Environment variable.
Environment variables can be scoped to the entire application or to a specific datasession. SET TALK is scoped to individual data sessions.

Set global environment variables at the beginning of the application startup.

Set data session specific environment variables when a new datasession is created.

SET PROCEDURE TO is an example of an environment variable scoped globally.

SET SAFETY, SET TALK, and SET NEAR are examples of environment variables scoped to the current datasession.

SET NEAR and SET EXACT improperly handled can totally screw up your application.

HTH