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 Procedures, and handling RAISE EXCEPTION.
Connecting to Informix
Supported Versions
The PowerBuilder native driver for Informix connectivity (IN9) is linked with
the IBM Informix ESQL C product to provide connectivity to the following IBM
Informix databases:
IBM Informix Dynamic Server (IDS) IBM Infor... (more)
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)
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)
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)
Designing and implementing an n-tier or Internet application is a complex
task, and issues resulting from errors in the runtime configuration or in the
application code are practically inevitable. Problem analysis and
troubleshooting are part art and part science. Therefore, although the
techniques we'll discuss are often helpful, the sheer diversity of client and
server environments precludes a single recipe for resolving all issues.
Part 1 (PBDJ, Vol. 12, issue 2) focused on problems that involve PowerBuilder
and that occur from the point of connectivity all the way through an E... (more)
Jim O'Neil is a Microsoft Developer Evangelist for the Northeast U.S. where he concentrates on the developer communities using Visual Studio .NET and the various .NET technologies. Prior to joining Microsoft, he was a Principal Systems Consultant and Principal Technical Support Engineer for Sybase, Inc., where he specialized in the PowerBuilder family of tools, EAServer, and Appeon for PowerBuilder.
Sue Poremba
Scott Sellers
Anthony Franco
Daniel Morris
Wayne Walls
Niki Acosta
Jereme Hancock
Oren Michels
Marvin Wheeler
Douglas Kim
