No it's not version based. If you launch VFP6 twice it'd be 2 separate sessions that each cannot access to tables opened exclusively by the other.
Even in one VFP if you create a form with private datasession and open a table exclusive in it, you wouldn't be able to access that table unless you set to form's datasession.
One workaround might be possible for you (if 2.6 app didn't explicitly used 'exclusive' clause and doing that wouldn't harm your 2.6 app in any way) :
Try to add a line to config.fp (or .fpw) of fx2.6 app - create config.fp if doesn't exist :

exclusive=off

In 2.6 there were only one datasession.
Cetin

>I can not reproduce this behavior. I have VFP 6.0 and VFP 7.0 running at the same time. If I open a dbf exclusive in one version, I can open it AGAIN in the same version, but I can not open it at all in the other version.
>
>>>If the table is used excl in VFP elsewhere I can use the table AGAIN.
>>>
>>>Ex. Use tmp AGAIN
>>>Works even if tmp is being used EXCL somewhere else by a VFP app, it is opened READ ONLY.
>>>
>>>However the same thing does not work if tmp is used by a 2.6 app. All I need to do is read from the table, not make any changes so READ ONLY is fine.
>>>
>>>The error I get is file access denied.
>>>
>>>Hope this clears the problem up.
>>
>>I think you are mistaken. Just try this then :
>>Launch VFP and open a table exclusive
>>Launch another one and try to use the same table in any way.
>>Can you ?
>>Cetin