Yes I understand your point, but it's by design since the beginning remember when we downloaded the first Sedna documents published by Microsoft? it was going to be only in the FFC since it was xbase code, it wasn't even worked at Microsoft or a direct Microsoft developer as far as I know, it was outsourcing.

Luis

>Hola Luis,
>
>As Doug said:
>
>The ReportListener returned by ReportOutput.APP (the first and second examples) isn't a base class ReportListener but one that has additional functionality (one of the classes in _ReportListener in the FFC folder). Your third example instantiates a base class ReportListener which doesn't know anything about rotation.
>
>As he said, this problem is not in the core EXE, but in the ReportListener class.
>
>My question is:
>As we're talking about an important feature that appears even in the report designer, would'nt it be better if the BASE CLASS REPORT LISTENER was updated too, to enable this feature for all the situations ?
>
>Regards
>
>Cesar
>
>>Hi Cesar, it is the expected behavior.
>>
>>The code to rotate it's in a subclass. Remember they didn't update VFP core EXE with new functionality, all the modifications were made in the Xbase components.
>>
>>Take care.
>>
>>Luis
>>
>>
>>>>The ReportListener returned by ReportOutput.APP (the first and second examples) isn't a base class ReportListener but one that has additional functionality (one of the classes in _ReportListener in the FFC folder). Your third example instantiates a base class ReportListener which doesn't know anything about rotation.
>>>
>>>
>>>Hi Doug,
>>>
>>>So, is it a bug ?
>>>Maybe they forgot to update it to handle the rotations ?
>>>
>>>Should we report this to MS or it is working as it should ?
>>>
>>>Thanks in advance
>>>
>>>Cesar