>>with an exclusive table ( a cursor is it ) not
>>
>>with a shared table yes:
>>- on every private datasession open the table in shared mode
>>
>>USE tablefilename.dbf IN 0 AGAIN ALIAS fixedname
>
>Yes this would be a possiblity. However, the form only opens cursors that are destroyed when the form closes. Having a table instead of a cursor creates files (memo included) on the pc that I didn't want to create.
>
>In particular this is for the menu editor that is now available in the download section -- a person suggested a feature to be able to cut-n-paste nodes from one menu to another menu. The current implementation of the menu editor uses a cursor for the menu while editing and another cursor to hold the "clipboard" of a menu node. This "clipboard" cursor is what is needed to be shared -- so it needs to be persisted and shared independently of the form instances. I would prefer not to have a file persist after the closing of all forms and subsequent shutdown of VFP. Using a cursor in a custom session is destroyed with the shutdown -- so it is "clean".
>
>Any thoughts?

This is a VFP design lack, but to share a datasession require a full VFP rewritingrewritting.

A possible way it that to add a clause to declare a cursor "global in application"
and then VFP can reopen it in every datasession.

CREATE SHARED CURSOR  ...
SELECT ... INTO SHARED CURSOR

this crate a exclusive file, but shareable within the process.

However, since Windows is too much simple,
if you kill the process or the PC, the temporary files remain in the filesystem,
and then you can use a temporary table.