Powerbuilder Upgrade Issues (PB 6.5 to PB 9.0.1)

Hello,

We are having some issues while trying to upgrade from PB
6.5 to PB 9.0.1 The database is Sybase .I was hoping if you
could post in any usergroups

Background:

There is a window  w_child inherited from w_parent.The
datasource of this dw_1 is a Stored Procedure that runs in
Sybase ASE 12.5
In ue_1 of w_parent there is a  dw_1.retrieve(arg1,arg2).
ue_1 of w_child extends ue_1of w_parent. In ue_1 of w_child
the code checks the condition dw_1.rowcount() >0  based on
which it decides on the execution flow.

Issue:

While running the application, no rows are getting
retrived.The same happens in debug mode too. [COLOR=Blue]But
when we have "dw_1.retrieve(arg1,arg2)" as a watch variable
in the debug mode the row is currectly getting
retrieved.[/COLOR]
In PB6.5 everything was working fine.

Please let me know if you have encountered a similar problem
and what the possible resolution could be.

Thanks,
Reni
[email protected]

maybe it's a good idea this in sybase.public.powerbuilder.general 
instead.

Ben


In article <[email protected]>, Reni says...
> Hello,
> 
> We are having some issues while trying to upgrade from PB
> 6.5 to PB 9.0.1 The database is Sybase .I was hoping if you
> could post in any usergroups
> 
> Background:
> 
> There is a window  w_child inherited from w_parent.The
> datasource of this dw_1 is a Stored Procedure that runs in
> Sybase ASE 12.5
> In ue_1 of w_parent there is a  dw_1.retrieve(arg1,arg2).
> ue_1 of w_child extends ue_1of w_parent. In ue_1 of w_child
> the code checks the condition dw_1.rowcount() >0  based on
> which it decides on the execution flow.
> 
> Issue:
> 
> While running the application, no rows are getting
> retrived.The same happens in debug mode too. [COLOR=Blue]But
> when we have "dw_1.retrieve(arg1,arg2)" as a watch variable
> in the debug mode the row is currectly getting
> retrieved.[/COLOR]
> In PB6.5 everything was working fine.
> 
> Please let me know if you have encountered a similar problem
> and what the possible resolution could be.
> 
> Thanks,
> Reni
> [email protected]
>