>(Dang my speedy fingers I just typed this response)
>>Well, after all these messages I got clearance of one thing: There is not an easy way to make this work.
>
>Depends on what you call "easy". :)
>
>Basically what you need to do is (in the absence of a generic way
>of referencing the cursors objects in a DE object) put this in the
>BeforeTableOpen event of the DE:
>
>This.Cursor1.CursorSource = gcPath + '\MyTable.dbf'
>
>and just make sure the gcPath is set to where ever the data is.
>
>Alternately you could use the same code without the gcPath and
>SET PATH TO (gcPath)
>in the calling program and (assuming MyTable.dbf is on the path) VFP will find
>it.
>
>>My decision will be to go back to the old foxpro style and put code to use and close tables, set orders and so on.
>>Isn't it clearer, easier & faster?
>>What's the advantage of using DataEnvironment after all?
>
>I read, in a document on optimizing VFP (it may even be in VFP Help), that
>using the DE to handle table setup is faster than using USE/SET RELATION code
>because the DE uses low level I/O operations, so whereas the ease and clarity
>of one method over another is subjective, the question of speed will pro'ly go
>to the DE.
>
>If you'd like me to locate that document on optimizing I'd be happy to look
>for it.
>
> ...kt

DE is probably a requirement to adapt private data session environment.