DBEdit Edition Comparison

DBEdit Edition Comparison

FeatureFree
Edition
Standard
Edition
Enterprise
Edition
Getting Data
Loading data from database tables, views, and stored procedures
JSON forms
Dynamic columnsxx
Saving Data
Saving changes to SQLite databases
Saving changes to server databases on local computers
Saving database table changes to databases on remote servers
Saving changes from views and stored procedures 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, MySQL, PostgreSQL, Snowflake
SQLite
Licensing
LicenseMITEULAEULA
Commercial use

Here’s a sample of the cell change handler, available only in the DBEdit Enterprise edition:

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 triggers these handlers on every cell change.

The change handlers can utilize predefined parameters like @column_name, @cell_value, and @cell_number_value, as well as column values using parameters with the same names, such as @id.

These handlers can update underlying tables or raise exceptions to prevent unwanted cell changes.

This website is using cookies. By continuing to browse, you give us your consent to our use of cookies as explained in our Cookie Policy.