Mel:

Absolutely no problem at all with what you are doing. As long as you call the CDE's release method (to really shut the CDE session down), all is well. Obviously, if you have the CDE creating a new private DS, if you want code to operate on the data in the private CDE DS, the code should be in the CDE's scope. I often create processing methods in the CDE or put a program based wrapper around a CDE class so that I can define additional methods that operate on the private CDE DS.

define class cdeSetupProg as cdeSetup
   
   function DoSomeJob  && This function is in the CDE's scope.
      *-- Code here.
   endfunc

enddefine

HTH

>The CodeMine doc's are a little weak on this one, so I thought I would ask it here just to make sure I am not missing something. I do call this many times throughout my program. Anyone know if it is a problem calling code like this over and over?
>
>I need to open some tables in a CDE through code. I then release the CDE. Is the following code what I need to do this, or am I missing some additional lines.
>

>LOCAL oCDE
>m.oCDE = CREATE('cdeSetup')
>m.oCDE.OpenAll()
>
>* Start doing My Stuff here
>
>* End doing My Stuff here
>
>m.oCDE.closeall()
>m.oCDE.Release()
>RELEASE m.oCDE
>

>Any thoughts are appreciated.
>
>Mel Cummings