Welcome!

Technology and Community

Jim O'Neil

Subscribe to Jim O'Neil: eMailAlertsEmail Alerts
Get Jim O'Neil via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Jim O'Neil

The release-defining feature of PowerBuilder 11 is its ability to deploy existing applications as .NET Windows Forms and Web Forms applications and components of business logic, namely custom-class user objects (NVOs), as .NET assemblies and Web Services. Although PowerBuilder's adoption of the .NET Framework represents a great leap forward for application developers, the implications of converting a desktop, client/server application to an ASP.NET Web application are significant. Those of you who have been working with PowerBuilder 11 know this first hand just from the sometimes daunting list of unsupported features that can appear in the Output window after deploying a .NET target (Figure 1). The unsupported features list contains valuable information necessary for you to successfully bring your application's functionality into the .NET world; however, the organi... (more)

PowerBuilder and EAServer: Uniting the .NET and J2EE Communities

In PowerBuilder 11.2, .NET meets J2EE head-on with the capability to deploy .NET Windows Forms and Web Forms applications (as well as assemblies and Web Services) that access Enterprise JavaBeans (EJBs) in Sybase’s own EAServer. As you’ll see over the course of this article, integrating these “competing” technologies is quite straightforward and leverages mechanisms that have been available since PowerBuilder 7. The enabling technology for the .NET to J2EE functionality in PowerBuilder is the new client support introduced in EAServer 6.1. The EAServer .NET runtime includes three... (more)

IBM & Informix

In this article we'll discuss connectivity requirements, Informix-specific data type processing, and the use of Informix stored procedures within the PowerBuilder environment. PowerBuilder offers developers four specific connectivity options for IBM Informix databases: Third-party Open Database Connectivity (ODBC) drivers Third-party Java Database Connectivity (JDBC) drivers Third-party OLE-DB providers The "native" driver available in the PowerBuilder Enterprise version In this article we'll focus on the last option and in Part 2 we'll discuss TEXT and BYTE data, Stored Procedur... (more)

PowerBuilder & Informix

In this article we'll discuss connectivity requirements, Informix-specific data type processing, and the use of Informix stored procedures within the PowerBuilder environment. PowerBuilder offers developers four specific connectivity options for IBM Informix databases: Third-party Open Database Connectivity (ODBC) drivers Third-party Java Database Connectivity (JDBC) drivers Third-party OLE-DB providers The "native" driver available in the PowerBuilder Enterprise version In this article we'll focus on the last option by discussing connectivity requirements, Informix-specific data... (more)

Introduction To PBNI

Have you ever thought of adding new features to PowerBuilder? Or wanted to call Java or .NET from PowerScript? Or imagined that you can call PowerScript from C++ or Java? With PBNI, you can do them all and more. PowerBuilder Native Interface (PBNI) is a standard interface for third parties to extend the functionality of PowerBuilder. PBNI is a valuable new addition to the PowerBuilder programmer's toolbox that allows developers to reach beyond the already feature-rich constructs of PowerScript and custom class user objects (commonly referred to as nonvisual objects or NVOs). The... (more)