>-- cut --
>
>>>

>>>...
>>>
>>>#IF WWC_USE_SQL_SYSTEMFILES
>>>   THIS.oSession=CREATE([WWC_SQLSESSION])
>>>   THIS.oSession.oSQL = THIS.oServer.oSQL
>>>#ELSE
>>>   THIS.oSession=CREATE([WWC_SESSION])
>>>   * New code
>>>   IF !empty(param4)
>>>      THIS.oSession.cTableName=param4
>>>   ENDIF
>>>   ***********
>>>#ENDIF
>>>
>>>...
>>>

>>>
>>>The ctableName prop is not used when WWC_USE_SQL_SYSTEMFILES is set.
>>>
>>>FWIW, Subclassing the wwProcess is also a good way to have your custom code always available...
>>>
>>>:)
>>
>>after carefully going through your suggestion i now agree.
>>I am just afraid to subclass the process class because it is involved in everything....
>>but I am about to give it a try...
>>
>>In the INITSESSION method...
>>after the
>>
>>THIS.oSession=CREATE([WWC_SESSION])
>>#ENDIF
>>
>>before the
>>
>>IF !THIS.oSession.IsValidSession(lcSessionId)
>>
>>line I am going to modify the THIS.oSession.cTableName and THIS.oSession.cDataPath properties...
>>
>>then it will attempt to open the wwSession table id prefer...
>>
>>Do you think this is a good place to make the modification?
>
>Yes.
>
>If you look at the wwSession class code, you will see that no table is open before any call to a method.
>So, it is safe to change this property just after the object creation :)

Have you dont this yourself personally?( am i a coward or what? )