Oracle was slow to introduce support for returning result sets from stored
procedures. When they finally did add such support, they did so in a manner
that was somewhat different than the approach used by other vendors.
This has a couple of consequences for PowerBuilder developers. The first is
that the PBDBMS approach was developed within PowerBuilder as an interim
workaround. The second is that using stored procedures to return result sets
is not as widespread a practice with Oracle databases as it is with other
This article (an excerpt from an upcoming book on PowerBuilder 9) is an
attempt to address this situation. The interim PBDBMS solution is going away.
In PowerBuilder 8, support for the PBDBMS was restricted to the O73 driver
and with PowerBuilder 9, support for it will be dropped completely. If you're
still using that old technique and n... (more)
In the early days of Java, a sample application called Java Pet Store was
introduced as a "blueprint and guideline" for Java development. A few years
later when Microsoft introduced .NET, they also provided a similar sample
application to demonstrate preferred methods of coding for .NET called .NET
Pet Shop. That has subsequently resulted in a bit of warfare as the two camps
attempted to demonstrate why their implementation was a better,
To provide a sample of using DataWindow.NET, I took a look at the .NET Pet
Shop with an eye toward demonstra... (more)
First there were the thin clients. Not the Internet thin clients, I'm talking
about the mainframe applications with dumb terminals. Everything ran on the
server; the client was basically there only to display and for input from the
Then PCs came along and a paradigm shift occurred toward thick clients.
Really thick clients in fact. Not only was the user interface running locally
on the PC, but often so was the data access layer, with the application
accessing local database files or perhaps a shared database file on the
network. Key reasons for the shift were a better user... (more)
Last month my editorial was about "must-have" improvements in PowerBuilder.
Well, shortly after that piece was written we got a sneak peak at the
enhancements coming in the next version of PowerBuilder.
I can't say I got everything on my list, but some of the coming attractions
are quite interesting.
Strangely enough, the peak came as a result of an ISUG tech cast on the
"compile to ASP.NET" feature that's supposed to be one of the major features
of PowerBuilder 11. That feature is dependent on ASP.NET 2.0, and Microsoft
recently announced a six-month slip in the ASP.NET 2.0 rele... (more)
In this article, we're going to look at how DataWindow.NET technology is a
simpler but more powerful way of formatting data in the presentation layer.
We'll be taking a sample application provided by Microsoft for .NET and
implementing it using DataWindow.NET technology. In this case, we're using
the Visual Basic .NET Code Sample: DataGrid Formatting sample application
available at www.microsoft.com/downloads/details.aspx?
The original sample was written to connect to the Microsoft Northwind sample
database. So you'll ... (more)