The OpenEdge Hive

This code was originally part of the Progress Open Source Software Exchange (POSSE) and governed by an open source license agreement. POSSE no longer exists, but you can download this code and use it in accordance with the terms and conditions of the PSDN Code Share License Agreement. Progress will not accept modifications to this code. However, if you want to share something you develop using this code, please submit it to PSDN Code Share.

This source code includes matches Progress Dynamics Version 2.1A. This code was originally part of the Progress Open Source Software Exchange (POSSE) and governed by an open source license agreement. POSSE no longer exists, but you can download this code and use it in accordance with the terms and conditions of the PSDN Code Share License Agreement. Progress will not accept modifications to this code. However, if you want to share something you develop using this code, please submit it to PSDN Code Share.

This source code includes matches Progress Dynamics Version 2.1A. This code was originally part of the Progress Open Source Software Exchange (POSSE) and governed by an open source license agreement. POSSE no longer exists, but you can download this code and use it in accordance with the terms and conditions of the PSDN Code Share License Agreement. Progress will not accept modifications to this code. However, if you want to share something you develop using this code, please submit it to PSDN Code Share.

V9 Application Development Methodology (ADM) development topics.

A separate zip file is also available which contains many of the sample 4GL procedures used by the examples in these papers. Note that code examples are not present in the zip file for newer papers, and that some errors in code for other papers are still to be corrected. In every case, the proper code needed to build the examples is illustrated in the documents themselves. There is no prescribed order for reading them, and the papers refer to one another in various ways, so it will be useful to make an effort to read all of them to get a complete view of the topics covered.

This code examples show how to take an existing Progress Report Builder report and recreate similar functionality with Crystal Reports.

These sample codes are in reference to the PSDN Web Seminar .NET Tips, Tricks and Traps.

If you have any questions regarding the sample code, please contact David Olson.

These sample codes are in reference to the PSDN Web Seminar 'From Progress to .NET and Back - The 'Round Trip' Process'.

If you have any questions regarding the sample code, please contact David Olson.

This example shows the use the assignQuerySelection and removeQuerySelection functions in the SDO to make use of dynamic query functionality.

added by:
Kimberly Craven

The Updateable Browse is one of the most important and widely accepted widgets in the GUI environment. It is similar to editable ActiveX Grid controls like Videosofts VsFlex or Microsofts Data Grid found in other GUI programming environments like Visual Basic and Delphi. However, these non-Progress Grids provide some enhanced features not found in the Updateable Browse widget like: drop-down lists (grids) from an updateable cell, or dynamically making an updateable cell non-updateable without making the entire column non-updateable. Well you can do the same in Progress too, and without learning any new non-Progress widget or control (and worrying about memory-leaks!). This Updateable Browse Enhancements implementation uses a GUI Button, Updateable Browse Widget with Free-Form Query, dynamic Browse Widget, and of course Frames.

added by:
Hansdip Bindra

This tool helps the DBA to detect when the size limit for a storage area is approaching a physical (addressing) limit. The analysis done by the tool provides a conservative view of storage area usage, i.e. there is a built-in safety margin in the reporting. The margin comes from space internal to a storage area that is actually available for the case of deleted and reused record-ids.

The download includes instructions on how to run the tool and interpret its results as well as a white paper, Best Practices For Managing Records-Per-Block Settings, which describes how to set records per block to achieve optimal performance. For more information on size limits for storage areas, see Chapter 3, OpenEdge RDBMS Limits of the OpenEdge Data Management: Database Design handbook.

The information and tools provided herein are provided "as is" without warranty of any kind. Progress Software Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Progress Software Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Progress Software Corporation or its suppliers have been advised of the possibility of such damages. Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

added by:
DB Struct Tool