<

DBGrid DeLuxe

Why another DBGrid?

  1. The original DBGrid for different reasons (unfortunately bugs, too) cannot be used for serious development.
  2. Other DBGrids are mostly parts of bundles.
  3. Our DBGrid is called "DeLuxe", and you may take this literally.
  4. A really flexible DBGrid, which takes only few resources enables you to write better software.

Better software, because most of the users handle grids pretty well.

But working with a grid, which can only navigate between data rows, maybe even without an orientation support by fixed data columns or a glimpse into memo fields, very soon becomes an annoying experience.

If the grid is showing information which is typically shown in a grid style, like item lists in offers, orders, invoices and delivery notes, the user certainly doesn't see, why he shouldn't edit the data right there.

The limitations of many DBGrids lead to complicated, non-intuitive constructions.

DBGrid DeLuxe can be configured in many details and programmed even further.

We have returned properties to it that seemed to be lost (e.g. compared to StringGrid).

Features which any good grid should have are now properties of your grid:



DBGrid DeLuxe

< Properties (details)...

Properties (overview):

Types are mentioned, if not yet obvious by the property's name.

Aside from the properties listed below DBGrid DeLuxe owns all the properties of TDBGrid. Special 32 bit features like TColumns and Multiselect are fully supported!

(*: Published and/or modified properties of T(Custom)DBGrid.)

public

published

New events:

New public methods:

Ancestor bugs/misbehavior fixed:

TInplaceMemoEditor:




 CONTENTS     Order