- Tim Ford
- PowerBuilder
- Thursday, 3 November 2022 02:09 PM UTC
Question to the PB Community:
We have a monolithic application consisting of a PowerBuilder frontend and C# .NET application server, both of which are tied to a MS SQL Server database. When the application was first written it was strictly PB, but over the years the app server was created, and much of the business logic and automated/background processing has been moved to it. However, the PB frontend still utilizes almost 300 windows and approximately 1500 datawindow/datastore objects (about a 3rd of which are for reports).
We have been tasked with moving all direct database connection from the PB client to the .NET app server. This means all 1500+ datawindow objects need to change how they retrieve and update their data so that they no longer establish a direct connection to the database. We had hoped to possibly leverage the webservice datawindow feature, but that has been deprecated and is now obsolete.
Can anyone recommend a course of action that would allow us to continue to use the datawindow objects in place within the client frontend application but move the corresponding CRUD functionality to our C# app server or some other centralized backend process? What would be considered the “best practice” for this scenario?
Thank you in advance for any advice.
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.