Events in ReadSoft Invoices

As invoices move through ReadSoft Invoices' production modules, events are fired at predefined points.

When an event is fired, ReadSoft Invoices checks to see whether you have defined a handler for the event. An event handler causes execution of a predefined VBA function, DLL function, COM object, or all of these.

When ReadSoft Invoices looks for an event handler, it searches in the current, specific context first, then in the more general context, until an event handler has been found or no more contexts exist. The current context specifies which objects are accessible at the moment an event is fired. These objects make up a hierarchy in which event handlers are searched.

There are four types of event handlers that you can define on four different levels.

Event mapping allows you to locally override event handlers defined on a higher level. For example, a field level event handler overrides an invoice level event handler for the same event.

Related topics

Where should the event handlers be placed?

Disable events