Welcome!

From the Editor-in-Chief of PowerBuilder Developer's Journal

Bruce Armstrong

Subscribe to Bruce Armstrong: eMailAlertsEmail Alerts
Get Bruce Armstrong via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Bruce Armstrong

Back in late 2002 I wrote an article on creating Web Services using PowerBuilder ("Implementing PowerBuilder-Based Web Services from PowerDynamo" http://pbdj.sys-con.com/read/42210.htm). It was based on a PowerBuilder 8.0 component deployed to EAServer called from Web pages based on PowerDynamo that used DOM to generate HTML from the XML from the Web Service. Because PowerBuilder 8.0 didn't support the native generation of XML, PowerScript was used to generate it manually. When PowerBuilder 9.0 came out, native XML was introduced. So were JSP targets. So I took that opportunity to rewrite the EAServer component with PowerBuilder 9.0 and rewrote the Web pages that accessed it using JSP. I wrote an article on how that was implemented in late 2003 ("Creating a Web Service with PowerBuilder" http://pbdj.sys-con.com/read/42590.htm). I was just updating the original comp... (more)

Using FOP to Handle Formatting of Large Text Blocks in DataWindow Output

It's been the bane of PowerBuilder development since day one. You have a DataWindow that contains one or more text blocks that, when previewed for printing or printed, span a page boundary. The result: the DataWindow incorrectly handles portions of the text. You may find some text on the first page that is repeated on the next page, or some text may be missing entirely, or the text may end up overwriting subsequent report objects. The bottom line is that the results are unusable, and it often takes a great deal of tweaking to get adequate results. The good news is that I found at... (more)

The Evolution of PowerBuilder .NET

Somebody was asking in the Sybase newsgroups "should I make the commitment to PB.NET?" and wanted non-marketing types to respond. I started to respond in the forums, but the eventual length of the response and its applicability to many other people resulted in my responding here. What PowerBuilder has always been good at - its differentiating factor - is allowing developers to rapidly build Windows client applications that are open with respect to the data source they work with. You can use other tools to do Windows client applications (e.g., C#, C++, etc.), but the primary adva... (more)

Implementing the Microsoft Rich Edit Control

What we needed to do was implement spell checking in the rich edit fields in our application (see Figures 1 and 2). To do that, we got a license for the Sentry Spelling Checker Engine from Wintertree Software (www.wintertree-software.com). The utility is easily implemented and works quite well on standard Rich Edit controls. However, the PowerBuilder Rich Edit control is an OEM version of an old third-party control that was popular before Microsoft introduced its Rich Edit control to the common controls. As a result, the messages and functions it supports are completely differen... (more)

Sybase TechWave 2005 Conference Review

This year TechWave 2005 took place at Caesars Palace in Las Vegas. For those of you who didn't make it, the following is a recap of the events, with a couple of thoughts and suggestions thrown in. Sunday, August 21 Test Your Sybase Knowledge Gameshow Four TeamSybase members (Millard Brown, Terry Voth, Mike Nicewarner, and myself) do battle against a team of Sybase employees. Each team took turns answering multiple-choice questions off a Jeopardy-style game board. Fifty percent of the questions were related to Sybase engineering and the rest were from other walks of life. There wer... (more)