Note: dbOvernet is built on top of MIDware technologies which have been exclusively licensed for commercial use; as a basic toolset for internal or non-commercial application, MIDware is still available at no cost.  There is an explantion of the relationship between MIDware and dbOverNet on their web site.

Vendor's Description (from Readme files, web site, etc.):

Database connectivity anywhere

dbOvernet's technology provides multi-tier database connectivity and communication (real-time, bi-directional, updateable, transaction-based data packet delivery) over LAN, WAN, intranet, extranet and internet carriers, or on standalone computers.

Through dbOvernet, businesses can implement enterprise-wide database solutions without regard to the host carrier, including complete intranet functionality and extranet capabilities like preferred customer and alliance partner database access.

Remote users become connected users and connected users can become remote users.

Thin client technology

dbOvernet embraces thin-client concepts. With a "download once" runtime library (1.5MB), fully functional executables are often less than 100k in size, with many quick applications in the 20k to 60k range. They load immediately over any host, making download and updates from the net a reality. Executables developed without the runtime library add about an extra 500KB, still thin by today's standards.

RAD development

Designed to run under TCP/IP protocol, dbOvernet offers RAD ease-of-use through 6 visual components. This exciting product allows developers, designers and businesses to develop far beyond the traditional client/server approach. Whole new, untapped markets await dbOvernetters. Have a look here. Domino-type intranet solutions are an affordable reality, as is software leasing over the internet. dbOvernet opens new worlds of new opportunities.

The thin client examples on this site demonstrate this new world, and suggest dozens of ways to take advantage of this exciting technology.

For intranet and internet webs, dbOvernet's straight-forward and familiar design environment eliminates the complexity and confusion found in typical solutions like CGI, ISAPI, DHTML, ASP and ActiveX. dbOvernet's multi-tier architecture, drop-and-go component technology, ease-of-use and low cost enables designers and businesses to implement solutions more quickly and for a fraction of the cost of solutions provided through other multi-tier products.

Delphi versions

dbOvernet runs on Delphi versions 3 and 4. Although we haven't tried it yet, the Standard edition ($99) can likely be used to develop client-side applications.

The Professional edition is required to develop server-side applications.    However, dbOvernet does not require the more expensive Client/Server Suite edition.

Database connections

Since dbOvernet is a multi-tier product with an open connectivity framework through our unique ServerObject class, database connectivity is not an issue.

Basically, any database that you can connect to and access data from is accessible to dbOvernet.

We provide templates and client-side applications to connect to databases using:

• The Inprise BDE, for either ODBC or direct drivers,
• ODBCExpress, to connect using that product's high-speed ODBC connectors,
• IB Objects, an alternative connector for Interbase databases.

Through the open architecture using our ServerObject class and existing server-side templates, (and often in just a few minutes), you can quickly develop connections to any datasource, whether it's SQL-based or not. You can access data warehouses, graphics and image data sources, document data storage, sequential filing systems, voice storage, anything.

The basic rule is: if you have a way to get at information using Delphi or any third-party tools, you can, in all likelihood, access and deliver it through dbOvernet.

Latest addition:

New component - TdbOClientDataSet. This one component encapsulates all 4 dbOvernet components used at the client side and is ideal for SQL work. The other components are still available for specialized functions that you might require.

TdbOClientDataset has:

New properties and methods to:

Designate the SQL expression through the property, SQL.

Automatically generate SQL expressions into the SQL property, from visually-designed properties. Can be overridden.

Takes information from the FieldLayout, Filter and ServerTableName properties to create the expression.

Automatically re-generate SQL expressions when any linked property changes at design or runtime. Can be overridden.

Provide a field name list for the automated SQL expression's SELECT statement. The list is created and inserted into the SQL expression automatically when you close the Field Layout Editor.

Provide filter specifications through the Filter property for the WHERE section of the SQL expression. (For instance: customerid like 'd'%.) Can be overridden.

Provide the key update field names and field types for automatic server updating through the property, KeyFieldNames. This property is automatically created when you select one or more fields in the Field Layout editor and designate them as the key update fields. Can be overridden.

Automate the designation of the server-side table associated with the TdbOClientDataSet through the property, ServerTableName. This field is automatically created when you enter a table name in the Field Layout editor or Import from the Field Layout Import dialog. Can be overridden.

Specify cached updating through the boolean property, CachedUpdates. If true, updates are automatically cached for subsequent processing through the new method, ApplyUpdates.

Control SQL requests through the property, Send.

Apply cached updates through the property, ApplyUpdates.

Access error handling through the event, OnDataDone.

Among the other features, not only can you can easily design runtime SQL expressions, but, in most cases, you don't even have to worry about creating a SQL expression - it's all done automatically.

This one component reduces everything to basically no code! Now the only components visible on a form are TdbOClientDataset and TDatasource (or TwwDatasource).

Further, you can override the automated features to directly specify any SQL expression. Execute complex queries to retrieve data from any tables and add expressions using the MetaSQL function, and dbOvernet will return both the metadata field layout information as well as the data.

Note, of course, that all the other dbOvernet components are still shipped with the product, so you have complete access to the entire dbOvernet architecture.

Our Comments:

dbOvernet adds a number of features not available in the MIDware code that it is based on; the biggest examples are the client-side SQL model, automated update capability, and a visual SQL builder.

kylecordes.com Headlines:

Refactoring some Factor code

What is the Best Git GUI (Client) for Windows?

I Admire the Ruby Community

Sometimes, Establishing Expertise Doesn?t Pay Off

Write your whole stack in JavaScript with Node.JS

Helping Our Customers Hire

SaaS: The Business Model ? Video

Take a Strategic Vacation

Standing Desk Experiment and Experiences

I?m Dreaming of a Better Social Media Client

The Prolog Story

When Will It Ship? Estimates and Promises