Progress

As you work with your application, you will want to know when Progress creates and updates indexes. Progress creates a new index entry for a record at the first occurrence of any one of the following:

-At the end of a statement in which Progress assigns values to all components of the index entry.

-At the end of the closest iterating subtransaction block in which the Progress 4GL creates the record.

-When Progress processes a VALIDATE statement.

-When Progress releases the record from the record buffer.

- At the end of the transaction in which Progress creates the record.

Progress updates an index at the end of any statement in which it changes the values for one or more index fields. Because Progress updates indexes immediately (at the end of an UPDATE statement), Progress immediately FINDs records in the order of the new index, while the data in the found record is unchanged. Progress changes the data in the record at the end of the scope of the record or when it releases the record.

Note: Progress does not update an index if the value you try to assign to the index field is the same as the current value of the index field. You can change the name of an index at any time.

You can also delete nonprimary indexes. However, before letting you delete a primary index, OpenEdge requires that you first designate another index as primary.

If there is only one index, you must create a new index before deleting the existing index. You cannot change any of the component definitions of an index. Instead, you must delete the index and re-create it using the modified component definitions.

Remember that OpenEdge assumes that the first index you create is the primary index, so create your primary index first. Using the 4GL

// DATABASE CONNECTION AND SELECTION VARIABLES - GET THESE FROM YOUR HOSTING COMPANY

$db_host = "localhost"; // PROBABLY THIS IS OK

$db_name = "??";

$db_user = "??";

$db_word = "??";

// WARNING: AN UNCAUGHT CONNECT ERROR WILL BARK OUT THE DB CREDENTIALS!

// $pdo = new PDO("mysql:host=$db_host;dbname=$db_name", $db_user, 'foo');

// OPEN A CONNECTION TO THE DATA BASE SERVER AND SELECT THE DB

$dsn = "mysql:host=$db_host;dbname=$db_name";

try

{

$pdo = new PDO($dsn, $db_user, $db_word);

}

catch(PDOException $exc)

{

var_dump($exc);

trigger_error($exc->getMessage(), E_USER_ERROR);

}

// SHOW THE PDO CONNECTION OBJECT

var_dump($pdo);

echo PHP_EOL;

Progress DataDirect Connect for ODBC is the most reliable, best performing ODBC driver for UNIX or Linux platforms:

Supports all major UNIX / Linux platforms for all major databases

Support for the z/Linux platform

Delivers the fastest, most scalable performance

Eliminates the need for database client libraries

Comes with an ODBC Driver Manager equivalent to Microsoft Windows ODBC Driver Manager

Supports Unicode and multi-language character set for best data integrity

Guarantees quality and reliability

ODBC Driver Support for All Major UNIX and Linux Platforms for All Major Databases

Supports IBM AIX, HP-UX, HP-UX IPF, and Sun Solaris, for a wide range of processors

Supports z/Linux, Red Hat Enterprise and SUSE Enterprise Server Linux distributions

Available for Oracle, DB2, SQL Server, Sybase, MySQL and more

After the ongoing debate earlier this autumn on the respective merits of Microsoft SQL Server and Progress – and whether it was possible for the two platforms to co-exist, Andrew Bremner (the managing director of Focus IT Ltd) has been in touch to say “My company has recently been granted a license to sell and support a realtime Progress to SQL Server (or Oracle) tool in the UK. This tool is developed and owned by Bravepoint in the US. Called Pro2SQL, this is mature, stable and working at many Progress sites across the US. I believe this product has the potential to end the Progress -v- SQL Server debate and allow end users to have the best of both worlds with their production database on Progress and their reporting in SQL Server.”

Our ODBC Drivers facillate the support of the above through the use of a custom "Data Dictionary File", this file is built by running the OpenLink provided Progress Program File "setup.p" situated in the "bin" sub-directory below the OpenLink base installation directory.

Once the script has been run, modify the OpenLink "Session Rules Book" using the gudilines displayed when the " setup.p" program completes.

Note: To make use of Progress Database Triggers please ensure that the Logical Database name to which your Triggers have been compiled matches the value that you provide to the "-ld" parameter when setting your Progress Database Connect options during the execution of "setup.p" .

Example:

If you have compiled your triggers against a database physically identified as "/usr/progress/demo.db" but logically identified as "mydemo" your "setup.p" Database Connection String would be:

/usr/progress/demo -ld mydemo

Your OpenLink Data Access Driver Suite (Multi-Tier Edition) consists of the following components, subdivided by prime function:

Client Components (OpenLink Database Agent Service Consumers)

Generic ODBC Driver (the file "oplodb32.dll" under windows or OS/2, "oplodbc.sl" or "oplodbc.so" under UNIX)

Generic Driver for JDBC™ (the files "opljdbc.zip" or "oplj dbc.jar")

Generic UDBC Driver (the end product of statically linking the file libudbc.o or dynamically linking the file "libudbc.so" or libudbc.sl" under UNIX)

Server Components (OpenLink Database Agent Service Providers)

OpenLink Request Broker (the file "oplrqb" or "oplrqb.exe" depending on operating system)

OpenLink Database Agents (the files "pro63e_sv" or "pro73c_sv" or "pro82a_sv" depending on major and minor Progress Database Server version and sub-version number)

The prime function of your OpenLink Components does not determine their physical location within your I.T. infrastructure, this is driven instead by the logical structure and nature of your database connectivity requirements.