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

This article offers a brief look into accessing the ODBC API from a PowerBuilder client application that views the tables and columns within any ODBC data source. The techniques shown here can be leveraged to provide capabilities such as ad-hoc reporting within your PowerBuilder applications. A Brief Overview of ODBC In 1989, the SQL Access Group (SAG), including representation from Oracle, Informix, Ingres, and Sun, was launched with the goal of defining standards for database interoperability. SAG took the lead in developing a SQL Call Level Interface (CLI) specification to define an application programming interface (API) that was vendor neutral, but provided essentially the same functionality as the proprietary embedded-SQL techniques that had been widely used to that point. The API was to be used by database vendors and other software providers in developing dri... (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)

.NET Features Analyzer

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... (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)

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)