Skip to main contentSkip to search
Powered by Zoomin Software. For more details please contactZoomin
Progress DocumentationProgress Documentation
Progress Documentation
  • Home
  • Home
  • EnglishČeštinaDeutsch (Germany)Español (Spain)FranzösischItaliano (Italy)Português (Brasil)日本語Русский (Russia)中文 (简体) (China)中文 (繁體, 台灣) (Taiwan)ar-AR
  • Login

Manage ABL Applications

Modify the application database

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
Table of Contents
  • ABL and R-code deployment and management
    • ABL Client Deployment Overview
      • Client deployment process
      • Client deployment and administration tasks
      • Additional deployment documentation
    • Manage Client Access to Databases
      • Connect clients to databases
        • Logical database names
        • Connection modes
        • Connection parameters
        • Connection techniques
          • Connect at startup
          • Connect from a procedure with the CONNECT statement
          • Connect with the Data Dictionary
          • Connect with the Data Administration tool
          • Connect with auto-connect
        • Connect to a non-OpenEdge database
        • Connection denials when the user count is exceeded
        • Reduce connection times
        • Start clients without connecting to a database
      • Select a working database for client use
        • Select a database with the Data Dictionary
        • Select a working database with the Data Dictionary when using a character interface
        • Select a database with the Data Administration tool
      • Disconnect databases for clients
        • Use the Data Dictionary to disconnect
        • Disconnect a database with the Data Dictionary when using a character interface
        • Use the Data Administration tool to disconnect
      • Learn about automatic database reconnect
        • Automatic database reconnect demo and code
        • Automatic database reconnection with OpenEdge replication
    • Maintain Application Security
      • Database table- and field-level security
        • Specify run-time permissions checking
        • Set table and field permissions
          • Example of personnel security
        • Determine the privileges of the blank user ID
      • Compile-time security
      • Run-time security
        • Application support
        • OpenEdge support
      • Operating system security
      • Designate a security administrator
        • ABL security administration
        • Auditing administration
        • Transparent data encryption administration
    • Maintain User Environments
      • Maintain the Windows user environment
        • Use the INI2REG utility
          • Use the command line interface
          • Search progress.ini and the Registry at startup
          • Maintain the progress.ini file
            • Startup section
            • Colors section
            • Default Window section
            • Fonts section
            • WinChar Startup section
            • WinChar Colors section
            • WinChar Default Window section
            • WinChar Keys section
            • Debug-Init section
            • Debug-Macros section
            • Debug-Buttons section
            • Keys section
            • Keymap section
            • Specify environment variables
        • Windows icons for running OpenEdge
        • Start the OpenEdge client
        • Modify client icons
        • Windows manifest file
        • Environments with OpenEdge .NET applications
          • .NET runtime
          • .NET assemblies
          • Code Access Security for network installs
      • Maintain the UNIX user environment
        • Maintain the PROTERMCAP file
        • PROTERMCAP syntax
          • General syntax
          • String syntax
          • Terminal name entries
        • Terminal capabilities entries
          • Functional listing of terminal capabilities
        • Vermont Views key function capabilities
        • Pointer to key functions
        • Specify colors
        • Specify the cursor motion capability
        • Specify keyboard mappings
          • Use key function syntax
          • UNIX stty control functions
        • Extended character support entries
        • Create a PROTERMCAP entry
        • Test terminal entries
        • Set up the terminal
        • Set the terminal type
        • Set the PROTERMCAP environment variable
        • Revert to the default PROTERMCAP file
        • Copy an existing terminal entry
    • Manage Client Performance
      • Procedure loading and execution
        • Use procedure libraries to improve r-code performance
        • Archives and code signing
        • R-code execution environment
          • Load and execute r-code from a file
          • Load and execute r-code from a standard procedure library
          • Load and execute r-code from a memory-mapped procedure library
          • Load and execute r-code from an archive library
          • Tune r-code execution
          • Tune standard procedure libraries
        • Monitor r-code activity
          • Interpret r-code usage statistics
          • Interpret r-code segment statistics
      • Temporary file I/O
      • Sorting I/O
    • Manage Libraries
      • Manage procedure libraries
        • Procedure library overview
        • Set up a procedure library
        • Use the PROLIB utility
          • Create a standard procedure library
          • Add files to a standard procedure library
          • Replace files in a standard procedure library
          • Delete files from a standard procedure library
          • Generate a memory-mapped procedure library
          • List the contents of a procedure library
          • Extract files from a standard procedure library
          • Extract files to your current directory
          • Compress a standard procedure library
          • PROLIB command examples
      • Manage archive libraries
        • Archive library overview
        • Archive library manifest attributes for security
        • Set up an archive library
        • Use the PROPACK utility
          • PROPACK command examples
        • Use the PROSIGN utility to sign and verify an archive
          • PROSIGN command examples
        • Use Ant tasks to create, sign, and verify archives
          • Ant tasks for archives examples
        • Access information in a manifest file
        • Troubleshoot archive libraries
        • Archive libraries shipped with OpenEdge
      • Run members from a library
      • Libraries and PROPATH
      • Memory and network considerations
      • Code page compatibility
    • Manage Print Devices
      • Print in OpenEdge
        • OUTPUT TO statement
        • OUTPUT THROUGH statement
      • Print in Windows
      • Set up output-routing
        • Use a startup procedure
        • Use an output-routing table
        • Use interactive output-routing
      • Print on UNIX
      • Configure a printer
        • Create a printer-control table
  • Deployment considerations
    • Choose a Code Format
      • Unencrypted source
        • Development product requirements for unencrypted source
        • User product requirements for unencrypted source
        • Advantages of unencrypted source
        • Possible drawbacks of unencrypted source
      • Encrypted source
        • Development product requirements for encrypted source
        • User product requirements for encrypted source
        • Advantages of encrypted source
        • Possible drawbacks of encrypted source
      • R-code
    • Initial Deployment
      • Deploy database structures and application files
      • Unencrypted source
      • Encrypted source
      • CRC r-code
      • Deploy OpenEdge .NET applications
        • Install .NET
        • Create an assemblies directory
        • Deploy application source code
    • Upgrades
      • Deploy upgrades
      • Modify the application procedures
        • Unencrypted source
        • Encrypted source files
        • CRC-based r-code
      • Modify the application database
        • Upgrade with updated .df and encrypted source
          • Use the upgrade template
        • Upgrade with updated .df and CRC-based r-code
        • OpenEdge product upgrades
    • Deployment Topics and Tasks
      • Encrypt source code procedures
        • XCODE utility
        • Prepare to use XCODE
        • Compilation
      • Use the BUNDLE utility
        • The bundle.c program
        • The unbundle.c program
        • Examples using BUNDLE
      • Dump and load
        • MKDUMP utility
        • Use your dump/reload facility
      • Restrict database access
  • R-code Features and Functions
    • R-code structure
      • Factors that affect r-code size
        • Action code segment
        • Initial value segment
      • R-code file segment layout
    • Procedure libraries and archives
    • Procedure libraries, archives, and PROPATH
    • R-code execution
      • Standard r-code execution environment
        • Standard execution sequence
        • Standard execution environment limits
        • Standard r-code segment management
      • Memory-mapped r-code execution environment
      • R-code directory management
      • R-code execution environment statistics
    • R-code portability
      • Display architectures
      • Database types
      • R-code version compatibility
      • R-code portability and operating system-specific statements
      • Byte order of integers in R-code
      • Examples of portable and nonportable r-code
    • Code page compatibility
    • Database CRCs and time stamps
      • CRC validation
        • CRC advantage
        • R-code execution with CRCs
      • CRC calculation
        • CRC calculation for tables
        • Database changes that affect CRCs
        • Database CRC changes that do not prevent r-code execution
        • CRC and time stamp availability
      • CRC-based deployment
      • R-code access authorization
    • R-code CRCs and procedure integrity
      • Assign CRCs to schema triggers
      • Validate CRCs for schema triggers
      • Signed archive files
      • RCODE-INFO handle
        • Get the r-code CRC
        • Example: Verify application r-code integrity
        • Example: Deploy schema triggers
        • Example: Determine which files are affected by a database change
        • Example: Determine which files differ between application versions
        • Example: Validation of r-code in a signed archive
  • OpenEdge Application Limits
    • Input/output limits
    • Sort limits
    • Name limits
    • Compiler limits
  • Deployment Utilities and Scripts
    • Templates
    • Utilities summary
    • DBRSTRCT utility
    • MKDUMP utility
    • XCODE utility
    • _tlr Module
Table of Contents

Modify the application database

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
  • Last Updated: February 11, 2026
  • 1 minute read
    • OpenEdge
    • Version 13.0
    • Documentation

Upgrading is more complicated when you have to change the database schema. If you are upgrading with unencrypted source, encrypted source, or CRC-based r-code, you can supply an incremental .df file and copies of the modified procedures.

Contents
  • Upgrade with updated .df and encrypted source
  • Upgrade with updated .df and CRC-based r-code
  • OpenEdge product upgrades
TitleResults for “How to create a CRG?”Also Available inAlert