>>Hi all,
>> Open VFP7, select OPEN from the Data Session Window. Dialog prompts for DBF, EXCLUSE box checked. Tables can be modified.
>> Run any program, without SET ECLU commands (already ON), open table(s) EXCLUSIVE, program ends with CLOSE DATABASES.
>> Now I try to OPEN a table from the Data Session window, the EXCLUSIVE box is NOT checked. Tables open READ_ONLY. No SET DATA commands or DATASESSION commands have been issued anytime.
>>
>>Q. Is there anywhere I can set this behavior of the Data Session?
>>
>>TIA,
>>Pete
>
>Pete,
>Tables didn't open read_only. If any table is used in a workarea where already in use then the behaviour you describe occurs (data session exclusive mark not resembling the current set exclusive). But I couldn't see open read_only behaviour. (Honestly I don't see it as a problem, almost forgot there were such a window). As a fix calling set exclusive explicitly after prg works :
>
>CLOSE DATABASES ALL
>lcExcl = SET("Exclusive")
>SET exclusive &lcExcl
>
>Cetin

Thanks Cetin,
I needed to verify that I wasn't going crazy. I opened and closed several DBF's from DATA SESSION right after starting VFP7. Only once did a DBF open Read-Only. I did not do anything else. Just opened and closed DBF's from DATA SESSION. All DBF's on a Novell server. Workstations are W2K. Problem doesn't exist in VFP6. I thought perhaps this was normal behavior for VFP7.

Here, 90% of our work is done from the COMMAND and DATA SESSION windows. Very few applications are written because we get different new clients every day. The few steady, repeating clients we have are the only ones with applications. Half of the six programmers have never written an application.

Pete