Marcus,

It's the private datasession. If you use the data environment but the default data session you won't run into this. The idea is that you could have several forms each running a private datasession. Not only does each form have its own set of work areas, it also has its own environment setting. To see which SET commands are scoped to the current datasession type HELP SET DATASESSION in the command window.

>Thanks Josh,
>Is this because of the private datasession, or using the dataenvironment to open the table?
>Thanks,
>Marcus.
>
>>Like many of the SET commands, SET TALK is scoped to the current data session. That means that when you start a new data session TALK reverts to its default setting which is ON. You'll need to SET TALK OFF in each form. You can do that using the BeforeOpenTables event of the data session or the Load event of the form.
>>
>>>We have never used the dataenvironment before, so this is the first time I've played with it. I added my free table to the environment, set my form to use private datasessions, and ran my form. To my dismay, set talk is now ON. There are values scrolling down my screen, and when its finished Set Talk goes back to OFF. I explicitly set Talk OFF in my code, but somehow it gets turned on. I removed the table from the dataenvironment and set talk remains off. Am I missing something? Thanks for any feedback.
>>>
>>>Marcus.