Evan,

If the GetModelName procedure is the only place in the Device Class that needs access to the Model class, just CREATEOBJECT the oModel inside that method and release it immediately after. Alternatively, Paul's suggestion is good. If, however, your Device class depends on oModel already existing when it instantiates, you are tightly-coupled.

>Is there any rule of thumb when balancing object coupling vs reusing existing objects? In the example below, the device object will return the model name, but it uses the model object to determine this.
>
>By tightly coupling the Device and Model object I am reusing the code to determine a model name, _BUT_ the Device object now relies on the Model object to exist.
>
>Here greatly simplified example:
>
>

>* Dept Class
>DEFINE CLASS Device AS Session
>	PROCEDURE GetModelName
>		PARAMETERS nDeviceId
>                * insert code to get fk_modelid
>                RETURN oModel.GetModelName(fk_modelid)
>	ENDPROC
>ENDDEFINE
>
>* Dept Model
>DEFINE CLASS Model AS Session
>	PROCEDURE GetModelName
>		PARAMETERS nModelId
>                SELECT model
>                SET ORDER TO id
>                SEEK nModelId
>                RETURN model.name
>	ENDPROC
>ENDDEFINE
>