Engineering applications that use active DBMSs (ADBMSs) often need to group activities into modes that are shifted during the execution of different tasks. This paper presents a mechanism for grouping rules into contexts that can be actived and deactivated dynamically. The ADBMS monitors only those events that affect rules of activated contexts. By dynamic rule grouping the set of mnitored rules can be changed during the transactions. In a static rule grouping the rules are associated with specific objects during the schema definition. A rule is always activated into a previously defined context. The same rule can be activated with different parameters and into several different context. Rules in a context are not enabled for triggering until the context is activared. However, rules can be directly activated into a previously activated context. When rule contexts are deactivated all the rules in that context are disabled from triggering. The user defined contexts can be checked at any time a transaction. Rule contexts can be used as a representation of coupling modes, where the ADBMS has built-in contexts for immediate, deffered, and detached rule processing. These built-in coupling modes are alwas active and are automatically checked by the ADBMS. Contexts and rules are first-class objects in the ADBMS. Database procedures can be defined that dynamically active and deactivate contexts and rules to support dynamically chaging behaviours of complex applications. THe context mechanism has been implemented in the AMOS ADBMS. The paper concludes with an example of a manufaturing control application that highlights the need for rule contexts.