DBEdit Edition Comparison
Special offer: 50% discount ($1440) for ODataDB Enterprise until May 31, 2024

DBEdit Edition Comparison

FeatureFreeStandardEnterprise
Getting data
Loading data from database tables, views, and stored procedures
JSON forms
Dynamic columnsxx
Saving data
Saving changes to SQLite and SQL Server Compact databases
Saving changes to server databases on local computers
Saving changes to databases on remote serversx
Saving changes to server databases using cell change handlersxx
Advanced features
Customizable context menus
Value lists for fields and parameters
Table views
Context windows and task panes
Data translation
Application workbooks from a database
Supported database platforms
SQL Server, Oracle, DB2, MySQL, PostgreSQL, NuoDB, Snowflake
SQLite, SQL Server Compact
Licensing
Commercial use

Here is a sample of the cell change handler available in the DBEdit Enterpise edition only:

CREATE PROCEDURE [xls17].[usp_sales_change]
    @column_name nvarchar(255) = NULL
    , @cell_value nvarchar(255) = NULL
    , @cell_number_value int = NULL
    , @id int = NULL
AS
BEGIN

SET NOCOUNT ON

IF @column_name = 'licensee'
    BEGIN
    UPDATE dbo17.sales SET licensee = @cell_value WHERE id = @id
    RETURN
    END

IF @column_name = 'product_id'
    BEGIN
    UPDATE dbo17.sales SET product_id = @cell_number_value WHERE id = @id
    RETURN
    END

END

DBEdit calls such handlers on every cell change.

The change handlers can use the predefined parameters like @column_name, @cell_value, or @cell_number_value, and column values using parameters with the same name, like @id.

The change handlers can update underlying tables or raise exceptions to prevent cell changes.