PBAngel,
From your description, I am "assuming" that you presently retrieve either one or zero rows of data. Depending on what you are using for a source for your nested datawindow, you should be able to modify the stored procedure to provide 0.00 values as a result set if there is...
We recently began using a v6.5 application on XP. We have encountered some problems related to the display. Configuring XP back to the older display format corrected most of the problems but we are now upgrading to PB8 and experience no such problems.
polyg,
I recently upgraded a powerbuilder 6.5 application. I encountered no messages during the upgrade. Following compile, all appeared to work fine. During subsequent testing, we found one problem in the code that failed under PB8 that worked ok in PB6.5. PB8 is a little less forgiving on...
PowerBuilderAngel,
Sorry for the confusion. The nested report I used consisted of a datawindow with two columns of data, a client attribute code and a associated attribute definition as the report source (i.e. code 100 = English). Even though only the attribute definition was visible in the...
I have found that when I use nested reports within a datawindow, I need to ensure that there are no fields on the nested datawindow that are not visible on the parent datawindow. i.e, I use nested reports within a report for displaying many-to-one relationships such as client attributes. The...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.