This is a group for keeping track of all ABL development support tools on the Hive
This page is intended to provide recognition for people who have contributed to the development of this utility. I will probably forget someone, for which apologies are offered, but I will try.
This section is intended to provide information on various questions which have come up in the use of this tool.
In addition to targeted queries related to specific enhancement or maintenance projects, we will be exploring a number of possible analysis functions including:
Some of the items on the roadmap include:
See below for pre-1.00 log
1.01 - Initial Proparse release. Includes tracking of shared variables
1.02 - Convert to case insensitive GUID keys
1.03 - Add all shared object types - buffer, browse, dataset, frame, menu, query,
stream, temp-table, variable, and work-table.
1.04 - Change compilable test to look for XREF
1.05 - Add Proparse buffer tracking to BuildBlocks to resolve buffer names to
tables
1.06 - Bug fixes in BuildBlocks
To run ABL2DB one runs launcher_abl2db.p whose configuration is discussed in the Configuration section. it sets up the overall log (one can add additional tracking if desired for debugging), creates the Driver class, initializes the Driver class with the configuration values, and then executes the Initialize() method which tests some preconditions, and the Process() method which does the actual work.
The primary tailoring occurs in the launch program, abl2db_launcher.p which is found at the top of the src directory. At the top of this program you will find a section of variable definitions labelled Application Specific Definitions. You need to edit the initial values for these definitions to match your application.
This tool has been designed for easily customization for site specific requirements. Installation instructions below assume installation in the context of PDSOE, but are easily adapted to batch operation, which is likely to be the norm for day to day operation.
The ABL compiler provides some valuable tools for analyzing individual compile units, but this information can become far more valuable if systematically gathered into a database and supplemented with other information and analysis tools. Presentation on this project can be found at http://cintegrity.com/content/Databasing-ABL-Code-and-Data-Relationships and http://cintegrity.com/content/How-Can-I-Fix-Applied-Use-ABL2DB%0B-Real-W... .
Hello,
datadiggerlib.p and wdatadigger.w use chr(160), which is a non breaking space in ASCII, in their logic. This should be changed to a variable cNBSP:
DEFINE VARIABLE cNBSP AS CHARACTER NO-UNDO. IF SESSION:CPINTERNAL = "utf-8" THEN ASSIGN cNBSP = chr(49824). ELSE ASSIGN cNBSP = chr(160).
Thanks,
Jan
ps.: The reason: chr(160) is invalid in utf-8, as a result the following code for prowin32 -cpinternal utf-8 :
MESSAGE REPLACE("a" + CHR(160) + "b", CHR(160), "~n") VIEW-AS ALERT-BOX INFO BUTTONS OK.
gives you this message:
Hi all.
Does anyone know what happend to the libxlsx project?
Regards
I added the directory in which the programs are and the output directory in the propath.
It is working for over an hour now for just 1 database.
Not a clue what is happening... (or not?)
Hi Experts,
AIX, OpenEdge 10.1A, Apache Tomcat 5.5
I am trying to deploy a web service but getting this error
Failed to deploy Web Service for :wsa1.
WSA request error: CONNECT FAILLURE.
OR
Failed to deploy Web Service for :wsa1.
WSA request error: REQUEST FAILLURE.
I tried all the steps mentioned by Progress knowledge base.
http://knowledgebase.progress.com/articles/Article/P19723
But could not get the right solution
Any help is highly appreciated.
Hello,
I'd like to test your XLSX-Tool (incl. generation of the template), but when I run the code the following error message appears:
"This copy of slibxlsx.p has expired."
Im using the "10.2b02-win-32bit-rcode.zip" on 10.2B06.
I hope you can explain/help!?
Thanks in advance,
Gerald