Hello,

suggested workaround to Classdefinition in PowerServer is create an event - in the object that you want to check - with the same name as the object itself.

For instance, if your class is n_cst_myobj, add an event 

event n_cst_myobj; // PS workaround

end event

and replace ClassDefinition with 

If lpo.triggerevent("n_cst_myobj") = 1 Then // lpo is powerobject of type n_cst_myobj

Best,

.m

What are you using the ClassDefinition() for?

Maybe it can be "worked around".

Hi Sim;

  Unfortunately, the "ClassDefinition" object class and related functionality in PB is not supported by PowerServer. There are no workarounds. However, you can bullet proof this common code in PB vs PS by the following ...

appeonextfuncs  lo_ps

lo_ps = Create appeonextfuncs

IF lo_ps.of_getClientType() = "PB" THEN

lcd_class = this.ClassDefinition   
li_vars = UpperBound ( lcd_class.VariableList )
For li_v = 1 to li_vars

// etc

ELSE

// Something different

END IF

HTH

Regards ... Chris