Indeed they do. But, as you say, private data sessions apply to all tables and cursors in a given session. Using private data sessions means you start from scratch, requiring you to re-open all tables, re-setting RELATIONs and FILTERs (if appropriate), etc. For me, there are times where this is more than I want to bother with, as all I want is a simple clean way to close any unneeded cursors when I'm done.

If I invoke a PRG to create a cursor for me, and if that PRG needs to create some other cursors along the way, there seems to be no consistent way to handle this.

I'm not expecting any change in the language here, just statement my preference for consistency -- if I can declare variables as LOCAL or PRIVATE, such that they disappear when the PRG or method finishes (and this declaration does not affect any other variables), I think it would be handy to have the same facility for cursors.

Cheers,

Jim


>>Too bad -- the ability to declare cursors as LOCAL or PRIVATE would be convenient, I think.
>>
>
>That's exactly what private data sessions give us, though the designation applies to all the tables and cursors in a given session.
>
>Tamar