- Brett Weaver
- PowerBuilder
- Friday, 29 September 2023 04:44 AM UTC
I feel a bit trepidatious asking this question as the last time I had a problem with PB2022 R2 my Laptop had a failing SSD and that was the fault.
Unfortunately, I have two important applications which are behaving differently under their R2 compilations rather than PB2022.
Application 1.. We have objects that are created using PFC (buttons) delivered as a power client which do not appear (Not visible but functional) for *some* users. I and my developer co-workers have no issues but *some* users have a problem where there is white space where a button should be. I have spent quite a bit of time on this but it works perfectly compiled under PB2022.
I guess I might be able to recode the windows but the following I can't do anything with
Application 2.. I have an application with a complex composite data window which all of a sudden starts producing blank pages between the pages with data. I have done all of the usual tricks looking for hidden fields etc.
I created a new composite report and started adding reports to it. When I get past six (the last having a lot of reports within it too) adding the seventh, all of a sudden it wants to go onto 2 pages (starts producing blanks between). It does not matter what datawindow I add to the report, even one that was previously added as report number 1 and caused no issues.
So.. I'm starting to feel like I need to revert.
This will also cause problems because we would like to use PB2022 R2's browser because it can access SharePoint Documents (can use permissions without having to log on) and other enhancements
** Note on Application 2 ** acting on a thought I went through all of the 15 nested reports on the sixth report and just hauled them in a smidge from the right-hand side (remember this code was unaltered for the last 6 months) then adding the seventh report to the composite went smoothly and the white pages were not generated. I must put in a request that appeon develop a check for page bleed. I wonder if it's because we have had new printer drivers loaded in the environment?
Thanks to you folk who commented - I appreciate it. I will work on the first issue and let you know how I get on.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.