R:BASE

04/21/2026

The New/Edit Stored Procedure dialog has been enhanced with a larger default window size, improving visibility of the argument list.

When creating a stored procedure, users define arguments including name, data type, and comments. These definitions are significant, as the number and data types of arguments provided during ex*****on must match those specified at creation.

The enhanced dialog allows for full visibility of all defined arguments and their associated comments. Additionally, user-adjusted window sizing is preserved between sessions, further improving usability and efficiency when managing stored procedures.

04/20/2026

A new Data Browser setting has been added to display the connected database name and path in the Data Browser title bar.

This option is especially beneficial for users who connect to multiple database instances that contain identical or similar table names, making it easier to distinguish between environments.

Note: The Database in Title Bar setting applies only to R:BASE sessions. Applications running under Runtime for R:BASE or R:Compiler for R:BASE will not display database information in the Data Browser title bar.

The following outlines what each General Option setting provides, allowing you to customize the appearance of the Data Browser to suit your preferences:
https://www.rbase.com/support/rsyntax/general_options.html

04/17/2026

The Enhanced DB Grid control now includes a new Indicator Width property, allowing the pointer column width to be adjusted as needed.

The indicator is the small pointer displayed in the first column of the grid that identifies the currently selected row. Its visibility is controlled by the Indicator option on the Properties tab.

With the addition of the Indicator Width property, the width of the indicator column can be customized to suit display preferences.

The following example demonstrates how to enable the indicator and adjust its width within a form EEP:

PROPERTY SHOWINDICATOR 'TRUE'
PROPERTY WIDTHOFINDICATOR 20

04/16/2026

The Keys/Indexes area of the Data Designer has been enhanced to display Column(s) by default within the list, making it easier to quickly identify indexed columns.

The Column(s) field shows the column name associated with each key or index. For multi-column indexes, the columns are displayed as a comma-separated list. The Column(s) panel remains available on the right side of the list, providing additional details such as column sort direction and size.

Sorting capabilities have also been added to the list, allowing column names to be located alphabetically. This enhancement is particularly useful when reviewing the Duplicate Factor list (sorted in descending order) to identify inefficient index definitions, where unnecessary or poorly defined indexes may be candidates for removal.

While this enhancement may appear minor, it significantly improves usability when working with tables that contain many keys or indexes. The benefit is especially noticeable when dealing with unnamed or multi-column indexes. Previously, users were required to manually select each index, review its column definitions, and remember or document the details.

04/15/2026

New column-level PROPERTY command parameters have been introduced to support loading BLOB data from a file and saving BLOB data to a file.

New Parameters:

. LOADFROMFILE
. SAVETOFILE

Syntax:

PROPERTY TABLE_COLUMN [TableName->ColumnName] LOADFROMFILE 'Value'

PROPERTY TABLE_COLUMN [TableName->ColumnName] SAVETOFILE 'Value'

Parameters:

. TABLE_COLUMN [TableName->ColumnName]
Specifies the table and column to modify.
. Value
Specifies the file name used for the load or save operation.

These new parameters enable developers to programmatically load file contents into a BLOB field or save BLOB data from the in-memory dataset to an external file.

Additional Column-Level Parameters:

. TEXTVALUE - Updates the field value
. SETTONULL - Sets the field value to NULL
. SHOWEDITOR - Launches the BLOB Editor for the column

Examples:

Example 01 – Load a BLOB from a file:
PROPERTY TABLE_COLUMN [Contact->ContPhoto] LOADFROMFILE 'NewPhoto.jpg'

Example 02 – Save BLOB data to a file:
PROPERTY TABLE_COLUMN [Contact->ContPhoto] SAVETOFILE 'CurrentPhoto.jpg'

Documentation Update
The "Managing BLOBs" technical document in the From The Edge series has been updated to reflect the enhanced PROPERTY command.

From The Edge:
https://www.razzak.com/fte/

"Managing BLOBs" Table of Contents:

. Part I: Introduction
. Part II: The Data Types
. Part III: R:BASE BLOB Editor
. Part IV: Displaying BLOBs in Forms
. Part V: Displaying BLOBs in Reports/Labels
. Part VI: Using Commands with BLOBs
. Part VII: Managing Database Stored Files
. Part VIII: BLOB Editor Settings
. Part IX: Sample Use of BLOBs

04/14/2026

The Data Browser has been enhanced to display extended field definition details in the status bar for the currently focused column.

The enhanced status bar pane may include one or more of the following field attributes:

. Primary Key
. Referenced Key indicator
. Foreign Key
. Index with sort direction
. AUTONUM with Next and Increment values
. Not NULL constraint

These additions complement the existing status bar information, which includes:

. Table Name
. Field Name
. Datatype and Length
. Computed and Expression details
. Comment/Description

This extended field information provides immediate context while browsing tables and tabbing through columns, improving efficiency when analyzing and understanding column data.

03/09/2026

The R:Expression Extractor plugin has been enhanced with several new features, allowing for more versatile extraction of database expressions.

New features include:

. Excel format output
. Selected expressions copied to the Windows clipboard
. Enhanced output file name logic
. Database name included in the output
. Connected database name displayed in the caption
. Maximized Extractor window

The R:Expression Extractor plugin extracts expressions from a database’s forms, reports, and labels. Expressions may be extracted from all forms, reports, and labels, or from a single selected object.

Available output options include a text file, the Windows clipboard, a variable, or an Excel spreadsheet file. In addition to extracting all expressions, specific selected expressions may also be copied directly to the clipboard.

When Form, Report, or Label is selected in the tree view, object totals and expression counts for the database are displayed.

When capturing expressions to a file, the file name is automatically generated based on the database name and the object type. When capturing expressions to the clipboard, use the paste functionality [Ctrl+V] to place the content in the desired destination.

When using the Variable output option, the extracted content is placed into the vRBTI_REE_RESULT variable, which uses the VARCHAR data type.

To launch the R:Expression Extractor, use the following syntax at the R> prompt.

Syntax:

PLUGIN RExpressionExtractor vResult

The R:Expression Extractor plugin is part of the R:BASE Plugin Power Pack:
https://www.rbase.com/products/pluginpowerpack/

03/06/2026

Enhancements have been implemented for R:BASE Technologies' Web Server products, R:WEB Reports 11 and R:WEB Gateway 11, allowing a R:BASE command file to be executed both before and after processing tasks are completed.

With R:WEB Reports, a command file may be executed either before or after a report is printed. With R:WEB Gateway, command files may be executed before or after an import or export process.

R:WEB Reports
R:WEB Reports prints database reports online using scripts called by a Web development language, without requiring R:BASE to be installed on the Web server. All twenty-one (21) output formats supported in R:BASE are also available in R:WEB Reports, providing flexible reporting options for users.

Parameters
RUN – Specifies a R:BASE command file to run prior to printing the report.
RUN_AFTER – Specifies a R:BASE command file to run after the report has been printed.

R:WEB Gateway
R:WEB Gateway provides online data import and export processing for R:BASE databases using scripts called by any Web development language, without requiring R:BASE to be installed on the Web server. The twenty-one (21) export types and seventeen (17) import types supported by R:WEB Gateway enable data exchange in a wide range of standard formats.

Parameters
RUN – Specifies a R:BASE command file to run prior to the import or export process.
RUN_AFTER – Specifies a R:BASE command file to run after the import or export process.

These tools automate the tasks of delivering reports and data in a variety of formats to end-users and clients from any location with Internet access.

https://www.rbase.com/products/rwebreports/
https://www.rbase.com/products/rwebgateway/

03/05/2026

R:Mail 11 supports OAuth 2.0 authorization for R:BASE applications that send email through Google and Microsoft Azure services. OAuth 2.0 allows applications to access API resources on behalf of a user without requiring the user’s credentials to be shared with the application.

Redirect URI Port Range
When configuring OAuth 2.0, a Redirect URI must be specified so that R:Mail can complete the authentication process and send email messages through a local redirect port. By default, R:Mail uses the following port range: 2132 – 2136

When sending email, R:Mail scans this range and selects the first available port. Because of this, a maximum of five simultaneous R:Mail application instances using OAuth 2.0 can send email at the same time on a single machine.

In environments with Remote Client installations or a large number of R:Mail users, the default five-port range may be exceeded, which can result in port conflicts. To address this, R:Mail now supports defining a custom redirect port range.

Custom Redirect Port Range
The desired ports must first be defined in the Redirect URI list within the Google or Microsoft Azure API configuration portal. After the Redirect URIs are configured, the same port values must be specified within the R:BASE application using the new ADD_OAUTH2_REDIR_PORT parameter:

ADD_OAUTH2_REDIR_PORT
Specifies redirected port values. The ports should be provided as a comma-separated list.

Example:

PLUGIN RMail vPort|ADD_OAUTH2_REDIR_PORT 2140, 2141, 2142, 2143, 2144

Important: The ports listed in ADD_OAUTH2_REDIR_PORT must also be included in the Redirect URI configuration within the Google or Microsoft Azure API portal.

Microsoft Azure Tenant ID Support
R:Mail has also been enhanced to support Tenant ID values when accessing Microsoft Azure API resources. The Tenant ID, also known as the Directory ID, identifies the organization associated with the Azure application. Some Microsoft Azure APIs require the Tenant/Directory ID to be specified as part of the authentication request. This value can now be provided in R:Mail using the new OAUTH2_TENANT_ID parameter.

OAUTH2_TENANT_ID
Specifies the Microsoft Azure Tenant (Directory) ID. If a Tenant ID is not specified, R:Mail will automatically use the Microsoft common endpoint.

R:BASE Technologies, Inc. markets and supports the relational database management system; R:BASE, for application development and business use, along with a variety other database-related software products. The company adheres to three basic principles in the design of its data management products:....

03/04/2026

The LOAD command has been enhanced to specify the starting row within a source file.

This new capability is especially useful when working with files that contain header information, comments, or other non-data rows at the beginning of the file that should not be imported into the table.

Syntax:

LOAD FROM AFTER ROWS

The AFTER ROWS parameter directs R:BASE to begin processing rows after skipping the first rows in the source file.

. must be a positive whole number.
. Processing begins with row in the file.

Example:

The following example loads the Calendar table while skipping the first 10 rows of the source file:

LOAD Calendar FROM CalUpdate275.txt AFTER 10 ROWS

If the file contains 1,685 total rows, R:BASE will skip the first 10 rows and load the remaining 1,675 rows into the Calendar table.

The AFTER ROWS parameter is particularly helpful when:

. The file includes column headers in the first row
. The file begins with descriptive text or comments
. The file contains metadata/headers that should not be imported
. A partial reload is required from a known row position

Notes:

. If AFTER ROWS is not specified, processing begins at row 1 (default behavior).
. If exceeds the number of rows in the file, no rows will be loaded.
. The parameter only affects the starting point; all subsequent rows are processed normally.

03/02/2026

The ON FIRST CONNECT, ON AFTER CONNECT, and ON BEFORE DISCONNECT commands have been enhanced to support calling a stored procedure when the event is triggered.

In addition, the ON BEFORE DISCONNECT event has been enhanced to fire even when a user session is forcefully closed using the RBAdmin plugin. This ensures that cleanup, logging, and auditing logic executes consistently, even during administrative session termination.

Example:

ON BEFORE DISCONNECT CALL RunLog() SAVE

This allows centralized event logic to be maintained within stored procedures rather than external command files, improving maintainability and control.

ON CONNECT/PACK Command
The ON CONNECT/PACK command allows you to run a code logic either before or after connecting to, or packing, a database. It supports executing:

. A command file
. Code stored in a table
. A stored procedure

Common Use Case
A typical use would be executing an AUTOCHK command before connecting to a database to verify integrity. By combining this with ABORT ON, the CONNECT or PACK operation can be conditionally aborted if the pre-connect validation fails. This provides administrators with greater control over database health and environment enforcement.

ON DISCONNECT / ON EXIT Commands
The ON DISCONNECT command allows ex*****on of logic before disconnecting from a database. The ON DISCONNECT/EXIT command extends this behavior by allowing ex*****on:

. After disconnecting from a database
. After closing the R:BASE session

These commands support:

. Command files
. Code stored in a table
. Stored procedures

Common Use Cases
Before Disconnecting

. Writing session logs
. Recording transaction summaries
. Auditing user activity

After Disconnecting / On Exit

. Reinforcing environment settings
. Writing final audit records
. Logging events within custom transaction tables