I have a function called "GuardarAExcel2()" which uses a step datawindow called "d_filafichero". With this function you generate an excel with the same visual aspect as your datawindow. I hope it helps you:

Example of use:

GuardarAExcel2( dw_1, "c:\Report.xls")
GuardarAExcel2( dw_1, "c:\Report.html")

Result in datawindow:

Enabling Drag & Drop from Outlook to PB using a 3rd Party (free) DLL

While trying to find a solution on how to be able to do a drag & drop from outlook into PB, I did find a DLL library from a 3rd party. The DLL was free to use (source code available to purchase) and it worked bot in x32 and x64 environments.

The reason why I'm posting this is that while searching from the internet for a solution, I didn't find that many useful pages. After two days of searching, I stumbled on this and thought thet other PB users can benefit from this.

The link to the DLL site is here https://www.catsoft.ch/#download

and on the page look for "Drag & Drop in PowerBuilder"

I have now other association to the 3rd party, other than that I use the DLL. I also askes permission for the posting from the 3rd party.

I'm happy with the DLL, and the users of our product also like the possibility to drag & drop emails or just a sibgle attachemnt, directly from Outlook to the PB application.

Kari

C# handles NULL quite different than PowerScript and SQL.
Same code in PowerScript and C# may have different outcome.

Introduction

PowerBuilder supports getting secured data from the OAuth 2.0 authorization server. The Bearer access token is supported, and the following grant types are supported:

• Authorization Code
• Implicit Flow
• Client Credentials
• Extension (or Refresh Token)
• Resource Owner Password

This document provides an example on how to set up OAuth 2.0 authorization workflow using the Authorization Code grant type in a PowerBuilder application.

Learning to define user events for items in the RibbonBar control feels like a lot of trial and error.
Different items support different events. Same event type requires different parameters.
My aim with this article is to take "... and error" out of your RibbonBar coding.
For each ribbon item type you get user event definitions that work.

Each ribbon item has its own XML element (here: Print Title is a CheckBox).
Each item binds specific user events via properties (here: Clicked on CheckBox binds to ue_PrintTitle)
Each user event must have the correct parameter list (here: Clicked event for CheckBox always requires al_handle while no other parameters allowed)
Each item type has its own PowerScript class and functions to obtain the object (here: Obtain class = RibbonCheckBoxItem via function GetCheckBox)
 

Why enhance JSON handling?

Reading and writing JSON in PowerBuilder is simple using PowerBuilder’s RESTClient object; however, the JSON needs to be in a two-dimensional format. But there are times when the JSON you are working with has multiple nested levels, especially if working with data from an external interface not under your control.

The PowerBuilder objects JSONParser and JSONGenerator can be used to parse or generate such JSON with multiple nested levels.  However, a key caveat is that the JSONParser and JSONGenerator require the JSON data to be accessed through “handles”.  For example, the getItemObject() returns a handle rather than the full JSON object.  Compared to an object-based approach, this handle-based approach requires more coding by the developer.

Did you know that Powerbuilder 2019 could run on Linux ?

Since Powerbuilder 2019 is now in 64 bit, it is now a lot easier to run on Linux using wine64