form5

### 1. Overview
 The `dbo.form5` table serves as a relational mapping or status tracking entity, specifically linking employees (`empcode`) to specific flags within a company (`compcode`) context. Based on the presence of `empcode`, this table is likely part of the Human Resources or Payroll module, potentially tracking specific categorical statuses (indicated by the `flag` column) for reporting or filtering purposes.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Primary key; unique record identifier. | | `PRIMARY KEY` |
 | **compcode** | string | YES | Physical Company Code. Links record to a specific legal entity. | e.g., "DAS" | `JOIN`, `WHERE` |
 | **empcode** | integer | YES | Unique Employee Identifier. | e.g., 10015 | `JOIN`, `FK` |
 | **flag** | string | YES | Status or categorical indicator for the employee. | e.g., "J" (Likely 'Junior', 'Joiner', or a specific payroll category) | `WHERE` |
 
 ---
 
 ### 3. Relationships & Join Map
 
 The table is primarily driven by Employee and Company identifiers. It serves as a secondary or status-based extension to the main employee master.
 
 #### Primary Joins (Authoritative):
 * **dbo.empmas**: Joined on `compcode` and `empcode`. This is the authoritative Employee Master table containing names, designations, and personal details.
 * **dbo.attandence**: Joined on `compcode` and `empcode`. Used to filter attendance records based on the specific `flag` defined in `form5`.
 * **dbo.attandenceregister**: Joined on `compcode` and `empcode`. Connects the category flag to monthly attendance aggregates.
 * **dbo.empshift**: Joined on `compcode` and `empcode`. Links the employee's category to their assigned work shifts.
 
 #### Metadata Joins:
 * **dbo.company**: Joined on `compcode`. Retrieves specific company details like GST, Address, and City.
 
 ---