Introduced in 1991 and patented in October 1996, PowerBuilder's DataWindow
technology remains one of the most flexible, dynamic, and versatile means for
data retrieval, modification, and presentation available in any development
tool. By launching DataWindow.NET along with PowerBuilder 10 later this year,
Sybase is continuing its commitment to the four-phased .NET strategy
announced in 2002.
DataWindow.NET is a separate product offering that brings PowerBuilder's
hallmark technology to the growing number of programmers in Microsoft's.NET
environment, including those using development tools such as Microsoft's
Visual Studio .NET, Borland's C#Builder, and the open source #develop
(SharpDevelop). In this two-part article we'll look at the overall design of
this exciting new product as well as work through a simple example in C#.
Author's note: This article was written ... (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)
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)
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)
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)
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.
David Lucas
Cathy Lopez
Shaul Efraim
Terence Martin Breslin
Cory Marchand
David Hughes
James Carlini
John Iffert
Dan Stolts
Joe Zeto
