pass1

### 1) Overview
 The `pass1` table serves as the primary user authentication and security repository within the SQL Server database. It stores login credentials (`username`, `password`), account status (`lock`), and session-related metadata such as the authorized `ComputerName` and `Location`. 
 
 This table is foundational for auditing, as many transaction tables in the schema (e.g., `RMproduct1`, `fghdr`, `jobhdr`) record the `username` to track who created or modified specific records.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Primary Key: Unique identifier for the user record. | | Primary Key for lookups. |
 | **compcode** | string | NO | Company Code: Used for multi-tenant or multi-branch isolation. | e.g., "DAS", "PDS" | Filter/Join key for company-specific data. |
 | **username** | string | NO | User ID: Unique identifier for login and audit trails. | e.g., "admin", "qc" | Join key for audit tracking in transaction tables. |
 | **password** | string | NO | User password (stored in plain text). | | Authentication verification. |
 | **ComputerName** | string | YES | The specific hardware name associated with this user's station. | e.g., "SERVER", "BOP2" | Security/Hardware-locking logic. |
 | **PwdModDate** | datetime | NO | Password Modification Date. | '1900-01-01' = Default/Null | Tracking password expiration or history. |
 | **Location** | string | YES | Physical work area or department. | | Organizational reporting. |
 | **lock** | string | NO | Account Lock Status: Indicates if the user is disabled. | 'N' (No), 'Y' (Yes) | Authentication logic filter. |
 | **SignImage** | string | YES | Path or binary data for a digital signature image. | | Printing signatures on reports/forms. |
 
 ---
 
 ### 3) Relationships & Join Map
 
 The `pass1` table acts as a central dimension for user identity. Most joins are based on a composite key of `compcode` and `username`.
 
 #### Authoritative Joins (SCHEMA_MAP confirmed):
 * **Audit Tracking**: Most transaction tables join on `compcode` and `username` to identify the record creator:
  * `dbo.RMproduct1 (compcode, username)`
  * `dbo.fghdr (compcode, username)`
  * `dbo.jobhdr (compcode, username)`
  * `dbo.rmincoming (compcode, username)`
  * `dbo.prodfhdr (compcode, username)`
 * **Security & Permissions**:
  * `dbo.Form_Active_Status (compcode, UserName)`: Controls which forms are active per user.
  * `dbo.PhyLocation (CompCode, username)`: Maps users to specific physical inventory locations.
  * `dbo.UserrightsHdr (compcode, usercode)`: **Likely** joins `pass1.username` to `UserrightsHdr.usercode`.
 * **Resource Ownership**:
  * `dbo.Vehiclemas (compcode, username)`: Identifies users responsible for specific vehicles.
  * `dbo.machine (compcode, username)`: Links machine operators or supervisors to assets.
 
 #### Likely Joins (Inference):
 * `dbo.Deletion_Log (CompCode, ERP_User)`: Join `pass1.username` to `ERP_User` to audit deletions.
 * `dbo.Backup_Taken_Log (compcode, userID)`: Join `pass1.username` to `userID` to see who performed backups.