[Properties (by Name)] [Methods (by Name)] [Events (by Name)]
Container for non-visual components.
Source position: classesh.inc line 2719
type TDataModule = class(TComponent) |
||
public |
||
constructor Create(); override; |
|
Create a new instance of a TDataModule. |
constructor CreateNew(); |
|
|
destructor Destroy; override; |
|
Destroys the TDataModule instance. |
procedure AfterConstruction; override; |
|
Overrides standard TObject behaviour. |
procedure BeforeDestruction; override; |
|
|
property DesignOffset: TPoint; [rw] |
|
Position property needed for manipulation in an IDE. |
property DesignSize: TPoint; [rw] |
|
Size property needed for manipulation in an IDE. |
|
Design Time PPI. |
|
published |
||
property OnCreate: TNotifyEvent; [rw] |
|
Event handler, called when the datamodule is created. |
property OnDestroy: TNotifyEvent; [rw] |
|
Event handler, called when the datamodule is destroyed. |
property OldCreateOrder: Boolean; [rw] |
|
Determines when OnCreate and OnDestroy are triggered. |
end; |
|
Container for non-visual components. |
|
| | | ||
|
Base class for all components that need owner-owned functionality. |
|
| | | ||
TPersistent,IUnknown,IInterfaceComponentReference |
|
Base class for streaming system and persistent properties. |
| | | ||
TObject,IFPObserved |
|
Base class of all classes. |
TDataModule is a container for non-visual objects which can be used in an IDE to group non-visual objects which can be used by various other containers (forms) in a project. Notably, data access components are typically stored on a datamodule. Web components and services can also be implemented as descendants of datamodules.
TDataModule introduces some events which make it easier to program, and provides the needed streaming capabilities for persistent storage.
An IDE will typically allow to create a descendant of TDataModule which contains non-visual components in it's published property list.
|
Event handler, called when the datamodule is created. |