>>>>>>I meant - I don't want to change code in the main application object class. I don't know what implications may arise if I change it. I wanted to only change the form's code assuming the application object is a black box.
>>>>>
>>>>>That is what I don't understand. Why would getting items say into an array would cause a change in application object class. You would do that from within your form.
>>>>>Cetin
>>>>
>>>>How can I get them into the array without changing code of the application object class? The method that produces the cursor I wanted to access is in application object and I didn't want to touch its code.
>>>
>>>You have already opted to make the change in your other reply where you liked the idea of attaching an object there.
>>>Cetin
>>
>>Attaching the extra object in run-time doesn't make a change in the class code, so IMHO, it's a big difference here.
>
>We have a seious communication problem:) OK how you prefer. You would get the array even w/o attaching something:)
>Cetin

Consider this

define class AppObject

procedure MakeCursor
  create cursor curTest (SomeField C(10))
  insert into curTest values ('Test')
 endproc
   
enddefine

main program of the application

public oAppObj

oAppObj = createobject('AppObject')


---------------------------------------------
form's code (form with private DS)

oAppObj.MakeCursor()

Now I need to get value of the curTest.SomeField. I can not change MakeCursor method in any way.