View Replies (1)
Is PowerBuilder 2022 incompatible with PowerBuilder 2017?
  1. Issue
  2.  PowerBuilder (Appeon)
0 Votes
  1. Gordon Weil
  2. PowerBuilder
  3. Wednesday, 1 February 2023 12:53 AM UTC

We have been stuck with version 2017 of PowerBuilder because every recent version of PowerBuilder has caused random crashes in our application.

During recent testing after migrating our main client application to PowerBuilder 2022 it became evident that the cause of the crashes was a currently running PowerBuilder application built with an older version of PowerBuilder.

I have been able to consistently reproduce the crashing behavior as long as I have an application built with an older version of PowerBuilder running before I start the PB2022 application. I have reproduced the behavior with an application built with PowerBuilder 2017 and also an app built with PowerBuilder 12.5. It does not appear to matter what application I am running, we have several, it only seems to require that the application was built with PB2017 or earlier.

We release our client application every year with an updated database. If we release our 2023 application built on PB 2022 it would be running concurrently with older versions built with PowerBuilder 2017 or earlier. This is not just an academic problem, it appears likely to affect our clients and be a serious issue.

I have not been able to duplicate the crashing behavior when running my application from the PB2022 IDE, but I can duplicate the behavior running the compiled app on the same machine I use with the PB2022 IDE.

We all run on recent versions of Windows 10, I will test on Windows 11 but have not yet. The PB2022 app was built using the latest MR, as you can see from the Event Viewer info:

Faulting module name: pbdwe.dll, version: 22.0.0.1892, time stamp: 0x6376455e
Exception code: 0xc0000005
Fault offset: 0x0027c7db
Faulting process id: 0x43c0
Faulting application start time: 0x01d935cac896f569
Faulting application path: C:\Program Files (x86)\NCC\NDSR 2023\ndsr.exe
Faulting module path: C:\Program Files (x86)\NCC\NDSR 2023\pbdwe.dll

ApplyTheme always returning -1 in production environment External Function with point to BSTR
Responses (1)
  1. Likes
  2. Latest
  3. Oldest

Find Questions by Tag

.EXE .NET 6.0 .NET Assembly .NET Core 3.1 .NET Core Framework .NET DataStore .NET Std Framework 32-bit 64-bit ADO.NET AEM AI Algorithm Amazon AWS Android Apache API APK App Store App Store (Apple) Appeon Workspace Appeon Xcelerator Plug-in Architecture Array ASE Asynchronous Methods Authentication AutoBuild AutoCompiler Automated Testing Automation AutoScript Azure Barcode Base64 Batch BigData BLOB Branch & Merge Browser Bug Build Button C# C# Class Importer C# Editor C# Model generator Calendar Camera Certificate Chrome Citrix Class Client Client/Server Cloud Cluster Collection COM Command Line Compiler Compression Computed Field Configuration Controls Cookies Cordova Crash Cross-Platform Crosstab CSharpAssembly CSharpObject CSS CSV Cursor Data Database Database Driver Database Painter Database Profile Database Provider DataObject DataSource DataStore DataStore (C#) DataStore (PS) DataType DataWindow DATE DATETIME DB2 Debug Debugger Debugging Deployment Design DLL DO-WHILE Dockable Docker Documentation DOUBLE Download DragDrop Edge Edit Style Editor Elevate Conference Email Embedded SQL Emulator Encoding Encryption Enhancement Request Entity Entity Framework ERP Error Event Event Handler Event Handling Excel Exception Export Expression External Functions F# Field File File Access Filter Firefox Firewall Font FOR-NEXT Foreground Format Function Garbage Collection GeoLocation Git Graph HANA Hash Header HTML/5 HTTP/S HTTPClient Icon IDE Identity IIS IMAPI Import InfoMaker Inheritance Installation Integer IntelliSense Interface Internet Internet Explorer iOS IPA iPad iPhone IWA J# Java JavaScript JBoss JDBC JOIN JSON JSONGenerator JSONParser Kestrel Label Lambda Large File LDAP Library License LINQ Linux OS Load Balancing Localization Localized PBVM Log In Log Out Logging LONG LONGLONG macOS MAPI Maps MDI Memory Memory Leak Menu Merge MessageBox Messagging Method Migration MIME TYPE Mobile Model ModelStore ModelStore (C#) MSOLEDBSQL Multi Threading MVC MySQL n-Tier Namespace NativePDF NVO OAuth ODATA ODBC Office Offline OLE OLEDB Online Open Source OpenAPI OpenSSL Oracle OrcaScript Other Outlook Output Package Parameter Patch PayPal PB Classic PB Native PB.NET PBC PBD PBDOM PBG PBJVM PBL PBNI PBORCA PBVM PBX PDF Performance Permission PFC Picture Pipeline Play Store (Google) Plugin Popup Port POST PostgreSQL PowerBuilder PowerBuilder (Appeon) PowerBuilder (SAP) PowerBuilder Compiler PowerBuilder Runtime PowerClient PowerScript (PS) PowerScript IDE PowerScript Migrator PowerServer PowerServer Mobile PowerServer Toolkit PowerServer Web PowerServerLabel Print Properties Proxy Publish PULL PUSH Query Regression Release Renew Resize Response REST Retrieve RibbonBar RibbonBar Builder Rich Text Roadmap RPC Runtime Packager SaaS Scaffolding Script SDI SDK Security Server Service Session Single Sign-on Size SMTP SMTPClient SnapDevelop SOAP Sort Source Code Speech Recognition SQL SQL Anywhere SQL Server SqlBuilder SqlExecutor SQLite SqlModelMapper Storage Stored Procedure Subscription SVN Swagger Syntax TabbedBar TabbedView Tablet TabPage Target TE Control Testing Text TFS Theme TIME Timer TLS/SSL Tomcat TortoiseGit TortoiseSVN Transaction Transparency Trial Trigger TRY-CATCH TX Control Type UI ULONG UltraLite Uninstall Unit Test Unit Testing UNIX OS Update Upgrade Upload URL User Center User Object UWP Validation VARCHAR Variable Versioning Visual Studio Visual Studio Code VM Voice Warning WCF Web API Web Extensions Web Service WebBrowser WebForms WebLogic WebSphere WildFly WinAPI Window Windows OS WinForms Wizard Workgroup Workspace WPF XCODE XHTML XML Zoom
✖

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.