Cybernomad
/
processSheet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

first commit

main
Jeremy 2025-06-15 20:48:33 -05:00
commit 25b28d5bcb
25 changed files with 2879 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.obsidian/app.json Normal file
View File

@ -0,0 +1 @@
{}

1
.obsidian/appearance.json Normal file
View File

@ -0,0 +1 @@
{}

31
.obsidian/core-plugins.json Normal file
View File

@ -0,0 +1,31 @@
{
"file-explorer": true,
"global-search": true,
"switcher": true,
"graph": true,
"backlink": true,
"canvas": true,
"outgoing-link": true,
"tag-pane": true,
"properties": false,
"page-preview": true,
"daily-notes": true,
"templates": true,
"note-composer": true,
"command-palette": true,
"slash-command": false,
"editor-status": true,
"bookmarks": true,
"markdown-importer": false,
"zk-prefixer": false,
"random-note": false,
"outline": true,
"word-count": true,
"slides": false,
"audio-recorder": false,
"workspaces": false,
"file-recovery": true,
"publish": false,
"sync": true,
"webviewer": false
}

22
.obsidian/graph.json Normal file
View File

@ -0,0 +1,22 @@
{
"collapse-filter": false,
"search": "",
"showTags": false,
"showAttachments": false,
"hideUnresolved": false,
"showOrphans": true,
"collapse-color-groups": true,
"colorGroups": [],
"collapse-display": true,
"showArrow": false,
"textFadeMultiplier": 0,
"nodeSizeMultiplier": 1,
"lineSizeMultiplier": 1,
"collapse-forces": true,
"centerStrength": 0.518713248970312,
"repelStrength": 10,
"linkStrength": 1,
"linkDistance": 250,
"scale": 0.7132754626224425,
"close": true
}

195
.obsidian/workspace.json Normal file
View File

@ -0,0 +1,195 @@
{
"main": {
"id": "8d88fb4ef392eb40",
"type": "split",
"children": [
{
"id": "533bbd10b9ea6571",
"type": "tabs",
"children": [
{
"id": "5a9721ec838ed738",
"type": "leaf",
"state": {
"type": "markdown",
"state": {
"file": "Queries/LogFileQ.md",
"mode": "source",
"source": false
},
"icon": "lucide-file",
"title": "LogFileQ"
}
}
]
}
],
"direction": "vertical"
},
"left": {
"id": "61325dae6ab858c9",
"type": "split",
"children": [
{
"id": "64f8c481d272fd2a",
"type": "tabs",
"children": [
{
"id": "1de591d1e1258ae7",
"type": "leaf",
"state": {
"type": "file-explorer",
"state": {
"sortOrder": "alphabetical",
"autoReveal": false
},
"icon": "lucide-folder-closed",
"title": "Files"
}
},
{
"id": "150ef2d72bcc35e8",
"type": "leaf",
"state": {
"type": "search",
"state": {
"query": "tag:#Database",
"matchingCase": false,
"explainSearch": false,
"collapseAll": false,
"extraContext": false,
"sortOrder": "alphabetical"
},
"icon": "lucide-search",
"title": "Search"
}
},
{
"id": "d977ecc07c2b0e20",
"type": "leaf",
"state": {
"type": "bookmarks",
"state": {},
"icon": "lucide-bookmark",
"title": "Bookmarks"
}
}
]
}
],
"direction": "horizontal",
"width": 300
},
"right": {
"id": "5fca8a1c9db9c80e",
"type": "split",
"children": [
{
"id": "dffd103026348a37",
"type": "tabs",
"children": [
{
"id": "5a96ebcf3fd59c87",
"type": "leaf",
"state": {
"type": "backlink",
"state": {
"file": "Queries/LogFileQ.md",
"collapseAll": false,
"extraContext": false,
"sortOrder": "alphabetical",
"showSearch": false,
"searchQuery": "",
"backlinkCollapsed": false,
"unlinkedCollapsed": true
},
"icon": "links-coming-in",
"title": "Backlinks for LogFileQ"
}
},
{
"id": "f54fa8589b6f40b8",
"type": "leaf",
"state": {
"type": "outgoing-link",
"state": {
"file": "Queries/LogFileQ.md",
"linksCollapsed": false,
"unlinkedCollapsed": true
},
"icon": "links-going-out",
"title": "Outgoing links from LogFileQ"
}
},
{
"id": "e08a41608a5a1e12",
"type": "leaf",
"state": {
"type": "tag",
"state": {
"sortOrder": "frequency",
"useHierarchy": true,
"showSearch": false,
"searchQuery": ""
},
"icon": "lucide-tags",
"title": "Tags"
}
},
{
"id": "0cbc95003df2b9fb",
"type": "leaf",
"state": {
"type": "outline",
"state": {
"file": "Queries/LogFileQ.md",
"followCursor": false,
"showSearch": false,
"searchQuery": ""
},
"icon": "lucide-list",
"title": "Outline of LogFileQ"
}
}
]
}
],
"direction": "horizontal",
"width": 300,
"collapsed": true
},
"left-ribbon": {
"hiddenItems": {
"switcher:Open quick switcher": false,
"graph:Open graph view": false,
"canvas:Create new canvas": false,
"daily-notes:Open today's daily note": false,
"templates:Insert template": false,
"command-palette:Open command palette": false
}
},
"active": "5a9721ec838ed738",
"lastOpenFiles": [
"README.md",
"Queries/AddnlQ1.md",
"Modules/Form_Process Sheet.md",
"VBA_Scripts/Process_Sheet_Form.md",
"Tables/MachineNames.md",
"Queries/MachinesQ1.md",
"Queries/PressBrakeQ1.md",
"Queries/UniversalQ.md",
"Tables/AddnlPROC.md",
"Tables/RMSFILES__MFWKP795.md",
"VBA_Scripts/Process Sheet_Dependencies.md",
"Process Sheet_Summary.md",
"RMSFILES_MFWKP795.md",
"Tables/RMSFILES__EGSSP1A0.md",
"Tables/Process.md",
"Tables/Machines.md",
"Tables/Labor.md",
"Queries/LogFileQ.md",
"Queries/PressBrakeQa.md",
"Modules/Custom_Functions.md",
"Modules/ModuleName.md"
]
}

732
Modules/Custom_Functions.md Normal file
View File

@ -0,0 +1,732 @@
# Custom_Functions Module
## Overview
The `Custom_Functions` module contains VBA functions for the manufacturing database.
```yaml
---
tags: [Access, Manufacturing, VBA]
created: 2025-06-09
---
```
`Custom_Functions`
=========================
## Overview
-----------
The `AddPartButton` function is used to add a button to the specified form for creating or editing a new part record in the manufacturing database.
## Parameters
-------------
### Required Arguments
| Argument | Data Type | Description |
| -------------------- | --------- | ------------------------------------------------------------------------ |
| `FormName` | String | The name of the form where the button will be added. |
| `ButtonLabel` | String | The label for the new button. |
| `FormSourceRecordID` | Integer | The ID of the record that this button will be linked to (if applicable). |
### Optional Arguments
| Argument | Data Type | Description |
| ------------- | --------- | -------------------------------------------------------------------------------------------- |
| `ButtonType` | Enum | The type of button to create (e.g., Command Button, Submit Button). Defaults to `CmdButton`. |
| `ButtonColor` | Integer | The color index for the button's background. Defaults to 0 (white). |
## Return Value
--------------
The function returns a boolean value indicating whether the button was successfully added.
## Usage
------
### Example
To add a button to the form `RMSFILES_MFWKP795`, use the following code:
```vba
AddPartButton FormName:=RMSFILES_MFWKP795, ButtonLabel:=\## Add_Additional_Process
```
### Overview
The `Add_Additional_Process` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
# Custom Functions
## logFile Function
### Overview
The `logFile` function is used to log production data in the manufacturing database, specifically for part processing in the RMSFILES\\#_MFWKP795 module.
### Parameters
| Parameter | Required | Data Type | Description |
| ---------------- | -------- | --------- | -------------------------------------------------- |
| `partNumber` | Yes | String | The unique identifier of the part being processed. |
| `productionDate` | No | Date/Time | The date and time of production (optional). |
| `partStatus` | No | String | The current status of the part (e.g., \\\\\` |
## Custom_Functions
### `HistoryR`
#### Overview
=====================================
The `HistoryR` function is used to retrieve production history data from the manufacturing database. This function is designed to provide detailed information about part processing, including dates of processing, quantities produced, and any relevant notes or comments.
#### Parameters
---------------
| Parameter | Data Type | Required |
| --------------------------------- | ---------- | -------- |
| `PartNumber` | String | Yes |
| `RMSFILEs\\#_MFWKP795` (optional) | Table Name | No |
#### Return Value
------------------
* A recordset containing production history data for the specified part number.
#### Usage
------------
To use this function, open the VBA editor, navigate to the form that contains the button or control calling the `HistoryR` function, and click the \# Delete_Part Function
======================
## Overview
\\\\
The `Delete_Part` function is used to delete a specific part from the manufacturing database in Access VBA. It takes into account the production history and current inventory levels, ensuring that parts are not deleted prematurely.
## Parameters
\\\\
- **Part_No**: The unique identifier of the part to be deleted (Required)
## Return Value
\\\\
None
## Usage
\\\\
1. Open the form's VBA code.
2. Navigate to the Custom_Functions module.
3. Call the `Delete_Part` function, passing the part number as an argument.
## Code
```vb
Sub Delete_Part(Part_No As String)
Dim db As DAO.Database
Dim rs As DAO.Recordset
' Connect to the database
Set db = CurrentDb()
' Open the RMSFILES table for modification
rs.Open \##
```
## Custom_Functions
### Edit_The_Shear_Files Function
#### Overview
The `Edit_The_Shear_Files` function is designed to manage and edit shear files in the RMSFILES database, specifically used in manufacturing applications for part processing.
#### Parameters
| Parameter | Type | Required |
| ------------- | ------- | -------- |
| `rshFileID` | Integer | Yes |
| `newFilePath` | String | No |
#### Return Value
No return value is expected; however, the function may modify records within the RMSFILES database.
#### Usage
This function can be called from a form's VBA code to edit shear files. The `rshFileID` parameter specifies the ID of the file to be edited, and the `newFilePath` parameter provides an alternative path for the file if needed.
```vba
Sub Edit_Shear_File()
Dim rshFile As New RMSFILES.rshFILEs
' Find existing shear file by ID
rshFile.FindFirst \Custom Functions
===============
```
### Find_By_PartNumber
#### Overview
The `Find_By_PartNumber` function is used to locate a specific part in the manufacturing database by its unique Part Number. This function is designed to be called from a form's VBA code, allowing users to quickly access and process parts as needed.
#### Parameters
| Parameter | Data Type | Required | Description |
| ------------ | --------- | -------- | ------------------------------------- |
| `PartNumber` | String | Yes | The unique Part Number to search for. |
#### Return Value
| Return Value | Data Type | Description |
| ------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------- |
| `PartDetails` | Recordset Object | A recordset containing the details of the found part. If no match is found, an empty recordset will be returned. |
#### Usage
To use this function, follow these steps:
1. Open the VBA editor for your form.
2. Navigate to the Custom Functions module (e.g., `RMSFILES#_MFWKP795`).
3. Call the `Find_By_PartNumber` function, passing in the desired Part Number as an argument.
Example code:
```vba
Sub ProcessPart()
Dim PartNumber As String
Set PartDetails = Find_By_PartNumber(PartNumber)
If Not PartDetails.EOF Then
' Process the found part...
Else
MsgBox
```
# **Custom Functions**
## Calculate_Button
```vba
Function Calculate_Button(Param As String)
Dim db As DAO.Database
Set db = CurrentDb()
' Implement the logic to calculate something here
Calculate_Button = \## GOTOPARTNUMBER
```
### Overview
The `GOTOPARTNUMBER` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
# Button291_Click Function
## Overview
---------------
The `Button291_Click` function is used to process a part in the manufacturing database, specifically for part number RMSFILES\\#_MFWKP795. This function is called when the \Custom Functions
### diskout Function
Overview
--------
The `diskout` function is used to determine the type of part being processed in a manufacturing database. This function is designed to be called from a form's VBA code to quickly and efficiently identify the type of part, which can then be used for production planning and tracking purposes.
Parameters
----------
### Input Parameters
| Parameter | Data Type | Description |
| --------- | --------- | ----------------------------------- |
| `PartID` | `Integer` | The ID of the part being processed. |
Return Value
------------
The function returns a string indicating the type of part being processed. The possible values are:
## UpdateGWs Function
### Overview
The `UpdateGWs` function is a VBA utility used in the manufacturing database to update global workstations (GWs) after a part has been processed. It ensures that the GW's status and inventory levels are updated accordingly.
### Parameters
| Parameter | Required | Data Type | Description |
| --------- | -------- | ------------ | ------------------------------------------------- |
| `gwID` | Yes | Long Integer | Unique identifier for the GW to update. |
| `status` | No | Variant | New status of the GW (e.g., \## LaserTapeGenerate |
### Overview
The `LaserTapeGenerate` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
## Custom Functions
### MoveFilesToPrefixLocation
#### Overview
The `MoveFilesToPrefixLocation` function is used to move files in the RMSFILES database to specific prefix locations based on their manufacturer's part number (MFWKP). This function is useful in a manufacturing context, where parts are processed and moved through different stages. By moving files to specific prefix locations, this function helps maintain organization and facilitates efficient processing of parts.
#### Parameters
| Parameter | Required | Data Type | Description |
| ---------------- | -------- | --------- | -------------------------------------------------- |
| `prefixLocation` | Yes | String | The desired prefix location for the file |
| `partNumber` | Yes | String | The manufacturer's part number (MFWKP) of the file |
#### Return Value
The function returns a boolean value indicating whether the file was successfully moved to its new location.
#### Usage
To use this function, you would call it from a form's VBA code like so:
```vba
Sub MoveFilesToPrefixLocationExample()
Dim prefixLocation As String
prefixLocation = \## Button200_Click
```
### Overview
The `Button200_Click` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
# Custom Functions
## CalcCNCRunTimes Function
### Overview
The `CalcCNCRunTimes` function is used in the manufacturing database to calculate the total run time for CNC machining operations on parts. This function is particularly useful in tracking and analyzing production times, which are essential for optimizing workflows and improving manufacturing efficiency.
### Purpose
In a manufacturing context, the `CalcCNCRunTimes` function helps to accurately record and summarize the time spent on CNC processing tasks. By providing a reliable method for calculating run times, this function supports data-driven decision making and process improvement initiatives.
### Parameters
| Parameter | Data Type | Required |
| ------------- | --------- | -------- |
| PartNumber | String | Yes |
| OperationName | String | No |
| StartDateTime | DateTime | Yes |
### Return Value
The `CalcCNCRunTimes` function returns the total run time for the specified part and operation, in seconds.
### Usage
To use this function from a form's VBA code:
```vba
Dim RunTime As Double
RunTime = CalcCNCRunTimes(RMSFILES\\#_MFWKP795, \## Button327_Click 'Laser Fun
```
### Overview
The `Button327_Click 'Laser Fun` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
Custom_Functions
================
## buttUpload_Click
### Overview
The `buttUpload_Click` function is used to upload parts to the manufacturing database from a production order. It retrieves the necessary data from the form's controls and calls the corresponding VBA functions in [[RMSFILES__MFWKP795]].
### Parameters
* None
### Return Value
None. The function does not return any value, but instead affects the records in the [[RMSFILES_MFWKP795]] table.
### Usage
1. Open the form and click on the \## CutTypeFormSettings
### Overview
The `CutTypeFormSettings` function is a custom VBA function used in the manufacturing database to retrieve and modify settings related to cutting types for parts processing.
### Parameters
| Parameter | Required | Data Type | Description |
| ------------------------- | -------- | --------- | --------------------------------------------------- |
| `cut_type_id` | Yes | Integer | Unique identifier for the cutting type. |
| `new_cutting_edge_length` | No | Decimal | New length of the cutting edge (in units). |
| `new_face_width` | No | Decimal | New face width (in units). |
| `save_changes` | No | Boolean | Whether to save changes made by this function call. |
### Return Value
The function returns a boolean value indicating whether the operation was successful.
### Usage
```vba
Sub ExampleUsage()
Dim cutTypeFormSettingsResult As Boolean
' Call the custom function with parameters
cutTypeFormSettings \\\\\`
```
# Find_By_MakeNumber Function
## Overview
The `Find_By_MakeNumber` function is used to retrieve data from the RMSDATABASE#_PARTINFO table based on the part make number. This function is designed to be used in a manufacturing context, where part processing and inventory management are critical.
## Parameters
| Parameter Name | Required? | Data Type |
| -------------- | --------- | ---------------------------------------- |
| MakeNumber | Yes | String |
| TableName | No | Variant (Default: RMSDATABASE#_PARTINFO) |
## Return Value
The function returns an array of records from the specified table that match the provided make number. If no records are found, an empty array is returned.
## Usage
To use this function in a form's VBA code:
1. Open the Visual Basic Editor.
2. In the Project Explorer, navigate to the Custom_Functions module.
3. Double-click the `Find_By_MakeNumber` function to view its code.
4. Replace the `MakeNumber` and `TableName` parameters as needed.
Example:
```vb
Sub FindPartDetails()
Dim makeNumber As String
makeNumber = \```
## CrossRef Function
### Overview
The `CrossRef` function is used to cross-reference part numbers in the manufacturing database. It retrieves the corresponding MFGPARTNUM value associated with a given RMSFILEID.
### Parameters
| Parameter | Required | Data Type | Description |
| --------- | -------- | ------------ | ------------------------------------------------------- |
| RMSFILEID | Yes | Long Integer | The unique identifier of the RMS file to be referenced. |
```
### Usage
Sub CrossReferencedPart()
Dim RMSFILEID As Long Integer
' Set the RMSFILEID value (Replace with actual input value)
RMSFILEID = 12345
' Call the CrossRef function
CrossRef RMSFILEID
' Access the returned MFGPARTNUM value
' Retrieve the corresponding part number from the database
End Sub
```
### Return Value
The `CrossRef` function returns a Long Integer value representing the associated MFGPARTNUM value.
| Returned Value | Description |
| -------------------- | ----------------------------------- |
| A valid Long Integer | The corresponding MFGPARTNUM value. |
| 0 | No matching MFGPARTNUM found. |
### Notes
The `CrossRef` function is designed to be used in a manufacturing context, such as part processing. It retrieves the corresponding MFGPARTNUM value for a given RMSFILEID, allowing users to easily access and manage part information.
To improve performance, consider using an index on the RMSFILEID column in the database table associated with `CrossRef`.
The function assumes that the RMSFILEID exists in the database. If no match is found, it returns 0.
Please note that this documentation is a general guide and may require adjustments based on specific requirements or version changes.
### Custom Functions
## Module: Custom_Functions
CrossReferencedPart()
```
Sub CrossRef(RMSFILEID As Long Integer)
Dim SQL As String
Dim rs As DAO.Recordset
' Connect to the database and execute the SQL query
Set rs = CurrentDb.OpenRecordset(\## PBFormView
```
### Overview
The `PBFormView` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
## PemPressView
### Overview
The `PemPressView` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
## ErrorMessages
### Overview
The `ErrorMessages` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
## Custom Functions
## gatherinfo Function
### Overview
The `gatherinfo` function is used to retrieve information about specific parts in the manufacturing database. It allows users to gather detailed information about part processing, including material usage, production time, and quality control metrics.
### Parameters
| Parameter | Data Type | Description |
| --------------------- | --------- | -------------------------------------------------------------------------------- |
| `PartNumber` | String | The unique identifier for the part being processed. |
| `RMSFILES.#_MFWKP795` | Table | The RMSFILES table containing information about parts, processes, and materials. |
### Return Value
The function returns a recordset containing information about the specified part, including:
* `PartNumber`
* `MaterialUsed`
* `ProductionTime`
* `QualityControlMetric`
### Usage
To use this function in a form's VBA code, follow these steps:
1. Open the Visual Basic Editor and navigate to the module containing the `gatherinfo` function.
2. Call the function by passing the part number as an argument: `gatherinfo PartNumber`
3. Assign the returned recordset to a variable or use it directly in your code.
### Notes
* The function assumes that the RMSFILES table has been populated with relevant data.
* If no matching part is found, the function returns an empty recordset.
* This function is intended for use in a manufacturing database context and may require custom modifications for other applications.
\\\\`\\\\`\\\\
```
Note: I've used Obsidian's markdown formatting conventions (escaped backticks `\\\\`) and replaced table names with their corresponding section headers (`# RMSFILES\\#_MFWKP795`).## AddPartButton
### Overview
The `AddPartButton` function supports manufacturing processes.
### Parameters
- To be documented
### Return Value
- To be documented
### Usage
- Called by [[VBA_Scripts/Process_Sheet_Form]]
### Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
#\\# Custom Functions
## HistoryR Function
### Overview
The `HistoryR` function is a custom VBA function designed to retrieve historical data related to part processing in a manufacturing database. It allows users to view the details of past production runs, including material used, time processed, and any quality control issues encountered.
### Parameters
#### Required Arguments:
* `PartNumber`: The number assigned to the specific part being processed.
* `RunDate`: The date range for which historical data is required (inclusive).
* `MaterialUsed`: The type of material being processed.
### Return Value
The function returns an array containing the following columns:
- `RunID`
- `PartNumber`
- `RunDate`
- `MaterialUsed`
- `TimeProcessed`# Custom Functions
## Delete_Part Function
### Overview
The `Delete_Part` VBA function is used in the manufacturing database to delete parts from the production line after they have been processed. This function is particularly useful for managing inventory levels and maintaining an up-to-date list of available parts.
### Parameters
| Parameter | Required? | Data Type | Description |
| --- | --- | --- | --- |
| `partNumber` | Yes | String | The unique identifier for the part to be deleted. |
### Return Value
The function returns a Boolean value indicating whether the deletion was successful (True) or not (False).
### Usage
To use this function, simply call it from your form's VBA code like so:
```vb
Delete_Part \\\# Custom Functions
## Button291_Click
### Overview
The `Button291_Click` function is used in a manufacturing database to process parts through the production line. It retrieves and updates relevant data from the database, triggering various actions such as logging, quality control checks, and inventory management.
### Parameters
None
### Return Value
The function does not return any value.
### Usage
To use the `Button291_Click` function in your form's VBA code:
1. Open the VBA editor for your form.
2. Click on the \# Custom Functions
## .Find_By_MakeNumber Function
### Overview
The `.Find_By_MakeNumber` function is used to locate specific parts in the manufacturing database based on their make number.
### Parameters
* `make_number`: Required - The make number of the part to be found.
* `db_table`: Optional (default: \\\#\\# Find_By_MakeNumber Function
=====================================
\\#\\# Overview
------------
The `Find_By_MakeNumber` function is used to locate specific records in the manufacturing database based on a unique part identifier (Make Number). This function is designed to streamline the part processing workflow, allowing users to quickly retrieve information about a particular component.
\\#\\# Parameters
--------------
### Required Parameters
* `makeNumber`: The Make Number of the part to be located.
### Optional Parameters
* `recordType` (optional): The type of record to search for. Defaults to `Records`.
* `fieldName` (optional): The field name to use when searching for the record. Defaults to `MakeNumber`.
\\#\\# Return Value
-----------------
The function returns a collection of records that match the specified Make Number and other criteria.
### Record Collection Structure
Each record in the collection contains the following fields:
* `ID`: The primary key of the record.
* `MakeNumber`: The Make Number associated with the record.
* `RecordType`: The type of record (e.g., `Parts`, `Inventory`, etc.).
* `OtherFields`: A list of other fields in the record.
\\#\\# Usage
------------
To use this function, simply call it from your form's VBA code and pass in the required parameters:
```vba
Dim records As Collection
Set records = Find_By_MakeNumber(makeNumber:=\

20
Modules/Form_Process Sheet.md Normal file
View File

@ -0,0 +1,20 @@
# Form_Process Sheet Module
## Overview
The `Form_Process Sheet` module contains VBA code for the manufacturing process.
## Procedures
- To be documented
## Usage
- Used by [[VBA_Scripts/Process_Sheet_Form]]
## Notes
Handles events and logic for the Process Sheet form.
```yaml
---
tags: [Access, Manufacturing, VBA]
created: 2025-06-13
---
```

1238
OllamaDebugLog.txt Normal file
View File

File diff suppressed because one or more lines are too long

17
Process Sheet_Summary.md Normal file
View File

@ -0,0 +1,17 @@
## Access Form: Process Sheet
# Tags: `#Access`, `#Manufacturing`, `#Form`
# Overview
The Process Sheet form in the manufacturing database is designed to collect and manage data related to production processes.
# Purpose
It provides a centralized platform for documenting, tracking, and analyzing various aspects of the manufacturing process, including:
- Process steps and variations
- Materials and supplies used
- Equipment maintenance records
- Quality control measures
The form enables efficient data collection, validation, and storage, supporting informed decision-making in the manufacturing department.

54
Queries/AddnlQ1.md Normal file
View File

@ -0,0 +1,54 @@
# Access
# Manufacturing
# Database
## Overview
The `AddnlQ1` query in the manufacturing database is used to retrieve a list of unique part details from the `AddnlProc` table.
## SQL Statement
```sql
SELECT DISTINCTROW AddnlProc.PartNumber, AddnlProc.OPCode, AddnlProc.ID, AddnlProc.Generated, AddnlProc.Description, AddnlProc.WC1, AddnlProc.WC2, AddnlProc.WC3, AddnlProc.WC4, AddnlProc.Machine, AddnlProc.CycleTime, AddnlProc.RunStd, Labor.LaborRate
FROM AddnlProc INNER JOIN Labor ON AddnlProc.WC2 = Labor.WC2
ORDER BY AddnlProc.PartNumber, AddnlProc.OPCode, AddnlProc.ID;
```
## Dependencies
This query depends on the following tables:
* `AddnlProc`: The main table containing part details.
* `Labor`: A reference table containing labor rates.
## Parameters
None. This query does not take any parameters.
## What it Does
The `AddnlQ1` query is used to retrieve a list of unique part details from the `AddnlProc` table, including but not limited to:
* Part number
* Operation code
* ID
* Generation date
* Description
* WC1 value
* WC2 value
* WC3 value
* WC4 value
* Machine used
* Cycle time
* Standard run time
* Labor rate
The query orders the results by part number, operation code, and ID.
## Notes
This query uses an inner join to link rows from `AddnlProc` with matching rows in `Labor` based on the WC2 value. This ensures that only parts with labor rates are included in the results.
The use of `DISTINCTROW` ensures that unique combinations of part number, operation code, and ID are returned, preventing duplicate rows from being displayed.
In a manufacturing context, this query can be used to generate reports or summaries of part data, including labor costs and machine usage.

42
Queries/LogFileQ.md Normal file
View File

@ -0,0 +1,42 @@
# Access Query: LogFileQ
## Overview
### Purpose
The `LogFileQ` query is used to retrieve specific data from the `LogFile` table in a manufacturing database.
### Description
This query retrieves part numbers (PN), actions taken, technicians involved, and timestamps associated with each log entry for parts processed on a given process sheet.
## SQL Statement
```sql
SELECT LogFile.PN, LogFile.Action, LogFile.Tech, LogFile.TimeStamp
FROM LogFile
WHERE (((LogFile.PN)=[forms]![Process Sheet]![PartNumber]))
ORDER BY LogFile.TimeStamp;
```
## Dependencies
The following tables are required for this query:
- `LogFile`
- `Forms` (for the process sheet form)
Note: The `Forms` table is used as a data source for the process sheet, which is a referenced value in the log file.
## Parameters
This query uses one parameter:
- `[forms]![Process Sheet]![PartNumber]`: This is a dynamic field that refers to the part number on the process sheet. It must be set before running the query.
Note: The use of dynamic fields allows for flexibility and ease of maintenance, as it can be updated directly within the form without modifying the query itself.
## What it Does
This query retrieves all log entries for parts processed on a specific process sheet, ordered by timestamp. The retrieved data includes:
- `PN` (part number)
- `Action`: Description or detail of the action taken on the part
- `Tech`: Technician involved in the action
- `TimeStamp`: Date and time of the action
## Notes
- This query assumes that the process sheet form has been configured correctly to link to the desired part numbers.
- The use of dynamic fields allows for easy modification of the query without affecting other parts of the database.
- Additional fields or calculations may be added to this query as needed, depending on the requirements of the manufacturing database.

31
Queries/MachinesQ1.md Normal file
View File

@ -0,0 +1,31 @@
# Access Query: MachinesQ1
# Tags: #Access, #Manufacturing, #Database
## Overview
MachinesQ1 is an Access query used to retrieve specific data from the 'Machines' table in a manufacturing database. The query aims to provide a list of unique part numbers along with corresponding machine names, cycle times, tools, and priming information.
## SQL Statement
```sql
SELECT DISTINCTROW Machines.PartNumber, Machines.MachineName, Machines.CycleTime, Machines.Tool, Machines.Prime
FROM Machines
ORDER BY Machines.PartNumber, Machines.MachineName;
```
## Dependencies
- The query depends on the 'Machines' table in the Access database.
- It requires access to the necessary permissions and data within the 'Machines' table.
## Parameters
None
## What it Does
The `MachinesQ1` query retrieves a list of unique machine part numbers, along with their respective machine names, cycle times, tools, and priming information. The results are sorted by part number and then by machine name for better organization and data retrieval.
## Notes
- The `DISTINCTROW` keyword ensures that each row returned in the result set is unique based on the specified columns.
- This query provides a quick way to access and manage part data, making it easier to perform tasks such as data analysis or reporting within the manufacturing database.

54
Queries/PressBrakeQ1.md Normal file
View File

@ -0,0 +1,54 @@
# Access Query Documentation
## #Access #Manufacturing #Database
### Overview
The PressBrakeQ1 query is a Microsoft Access database query used to retrieve distinct part data from the `PressBrakeOPs` table in a manufacturing database.
### SQL Statement
```sql
SELECT DISTINCTROW
PressBrakeOPs.PartNumber,
PressBrakeOPs.OpCode,
PressBrakeOPs.Step,
PressBrakeOPs.Angle,
PressBrakeOPs.Comment,
PressBrakeOPs.Breaks,
PressBrakeOPs.Hits
FROM
PressBrakeOPs
ORDER BY
PressBrakeOPs.PartNumber,
PressBrakeOPs.OpCode,
PressBrakeOPs.Step;
```
### Dependencies
* `PressBrakeOPs` table in the database.
### Parameters
None. The query relies on data already present in the `PressBrakeOPs` table.
### What it Does
The PressBrakeQ1 query is designed to retrieve distinct part information from the manufacturing database, including:
* Part number
* Operation code
* Step
* Angle
* Comment
* Breaks
* Hits
These values are ordered in ascending order by part number, operation code, and step. The `DISTINCTROW` clause ensures that duplicate rows are removed from the query results.
In a manufacturing context, this query can be used to retrieve data for part-specific operations or to analyze production trends based on part characteristics.
### Notes
* This query may need to be updated if the schema of the `PressBrakeOPs` table changes.
* Depending on the size of the database and the complexity of the queries, optimizing this query might require further analysis and optimization techniques.

32
Queries/PressBrakeQa.md Normal file
View File

@ -0,0 +1,32 @@
# PressBrakeQa Query
## Overview
The `PressBrakeQa` query retrieves data for the manufacturing process.
## SQL Statement
```sql
SELECT PressBrakes.PressBrake, PressBrakes.PBType, PressBrakes.CNC, PressBrakes.WC2, PressBrakes.WC3, PressBrakes.WC4
FROM PressBrakes
WHERE (((PressBrakes.CNC)=[Forms]![Process Sheet]![txtPrime] Or (PressBrakes.CNC) Is Null Or (PressBrakes.CNC)="ALL"))
ORDER BY PressBrakes.PBType DESC;
```
## Dependencies
- To be documented
## Parameters
- None
## What it Does
Provides data for the PressBrake control.
## Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
```yaml
---
tags: [Access, Manufacturing, Database]
created: 2025-06-13
---
```

31
Queries/UniversalQ.md Normal file
View File

@ -0,0 +1,31 @@
# UniversalQ Query
## Overview
The `UniversalQ` query retrieves data for the manufacturing process.
## SQL Statement
```sql
SELECT DISTINCTROW Process.*
FROM Process
ORDER BY Left$(Right$(" "+[Process].[PartNumber],5),4), Right$([PartNumber],1) DESC;
```
## Dependencies
- To be documented
## Parameters
- None
## What it Does
Retrieves data for the form's record source.
## Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
```yaml
---
tags: [Access, Manufacturing, Database]
created: 2025-06-13
---
```

0
README.md Normal file
View File

0
RMSFILES_MFWKP795.md Normal file
View File

26
Tables/AddnlPROC.md Normal file
View File

@ -0,0 +1,26 @@
# AddnlPROC
---
## Record Count
- 266657
## Fields
| Field Name | Type | Size | Description |
| ----------- | ------- | ---- | ----------- |
| PartNumber | Text | 11 | - |
| ID | Long | 4 | - |
| Generated | Boolean | 1 | - |
| OPCode | Text | 4 | - |
| Description | Memo | - | - |
| WC1 | Text | 3 | - |
| WC2 | Text | 3 | - |
| WC3 | Text | 3 | - |
| WC4 | Text | 3 | - |
| Machine | Text | 30 | - |
| CycleTime | Double | 8 | - |
| RunStd | Double | 8 | - |
## Indexes
| Index Name | Fields | Primary Key | Unique |
| ------------ | ---------- | ----------- | ------ |
| AddnlProcWC2 | WC2 | No | No |
| ID | ID | No | No |
| OPCode | OPCode | No | No |
| PartNumber | PartNumber | No | No |

13
Tables/Labor.md Normal file
View File

@ -0,0 +1,13 @@
# Labor
---
## Record Count
- 42
## Fields
| Field Name | Type | Size | Description |
|------------|------|------|-------------|
| WC2 | Text | 3 | - |
| LaborRate | Double | 8 | - |
## Indexes
| Index Name | Fields | Primary Key | Unique |
|------------|--------|-------------|--------|
| PrimaryKey | WC2 | Yes | Yes |

14
Tables/MachineNames.md Normal file
View File

@ -0,0 +1,14 @@
# #Access #Manufacturing #Database
## Overview
The `MachineNames` table is a critical component of a manufacturing database, playing a pivotal role in managing parts and their corresponding machines. This table serves as a lookup mechanism to quickly retrieve machine information for a specific part, facilitating efficient production planning and inventory management.
## Fields
### MachineName
- **Type**: Text
- **Size**: 20 characters
- **Description**: Unique identifier for the machine.
### WC2
- **Type**: Text
- **Size**: 3 characters
- **Description**: Second-character unique identifier for part coding (for example, \

59
Tables/Machines.md Normal file
View File

@ -0,0 +1,59 @@
\\# Access Database Documentation
=============================
\\# Tags: #Access, #Manufacturing, #Database
## Overview
The 'Machines' table in the manufacturing database is a crucial component for managing machine-related data in a production environment. It tracks information about each machine, including its part number, cycle time, tool usage, and whether it's prime or not.
## Fields
### PartNumber
\\#.description: Unique identifier for a specific machine.
\\#type: Text (max 20 characters)
\\#.size: 20
\\#.description: -
### MachineName
\\#.description: Unique identifier for a specific machine.
\\#type: Text (max 20 characters)
\\#.size: 20
\\#.description: -
### CycleTime
\\#.description: Average time required to complete a cycle on the machine.
\\#type: Single
\\#.size: 4
\\#.description: -
### Tool
\\#.description: Type of tool used on the machine.
\\#type: Text (max 3 characters)
\\#.size: 3
\\#.description: -
### Prime
\\#.description: Indicates whether the machine is prime or not.
\\#type: Boolean
\\#.size: 1
\\#.description: -
## Indexes
The following indexes are created on the 'Machines' table:
| Index Name | Fields | Primary Key | Unique |
|------------|--------|-------------|--------|
| PartNumber | +PartNumber;+MachineName | No | No |
This composite index is used to quickly locate a specific machine based on its part number and machine name.
## Usage
In the manufacturing database, the 'Machines' table is used to track machine performance data. It's essential for maintaining accurate records of cycle times, tool usage, and machine status. This information can be used to optimize production processes, reduce downtime, and improve overall efficiency.
## Notes
- The use of Boolean data type for the 'Prime' field allows for efficient storage and querying of machine statuses.
- The composite index on 'PartNumber' and 'MachineName' enables fast lookup of machines by these identifiers, facilitating easier maintenance and tracking of machine performance.

33
Tables/Process.md Normal file
View File

@ -0,0 +1,33 @@
# Access
# Manufacturing
# Database
## Overview
The `Process` table is a central component of the manufacturing database, responsible for tracking part-related data and processes. It serves as a comprehensive repository for managing various aspects of parts production, enabling efficient tracking and analysis.
## Fields
### PartNumber
* Type: Text
* Size: 11
* Description: Unique identifier for each part number.
### PhantomNumber
* Type: Text
* Size: 11
* Description: Alternate identifier used when actual material is not available.
### Warehouse
* Type: Text
* Size: 2
* Description: Code representing the storage location of the parts.
### Flag
* Type: Text
* Size: 5
* Description: Special flag indicating specific actions or events (e.g., \

89
Tables/RMSFILES__EGSSP1A0.md Normal file
View File

@ -0,0 +1,89 @@
# RMSFILES#_EGSSP1A0 Table
## Overview
The `RMSFILES#_EGSSP1A0` table stores data for the manufacturing process.
## Fields
| Field Name | Type | Size | Description |
|------------|------|------|-------------|
| CURPN | Text | 15 | - |
| NEWPN | Text | 15 | - |
| NCDRW | Text | 1 | - |
| ENTYR | Integer | 2 | - |
| ENTMN | Integer | 2 | - |
| ENTDY | Integer | 2 | - |
| ENTTM | Long | 4 | - |
| ENTUS | Text | 10 | - |
| ENTWS | Text | 10 | - |
| PMFLG | Text | 1 | - |
| PMDYR | Integer | 2 | - |
| PMDMN | Integer | 2 | - |
| PMDDY | Integer | 2 | - |
| PMDTM | Long | 4 | - |
| PMDUS | Text | 10 | - |
| PMDWS | Text | 10 | - |
| PMDPG | Text | 10 | - |
| RMFLG | Text | 1 | - |
| RMDYR | Integer | 2 | - |
| RMDMN | Integer | 2 | - |
| RMDDY | Integer | 2 | - |
| RMDTM | Long | 4 | - |
| RMDUS | Text | 10 | - |
| RMDWS | Text | 10 | - |
| RMDPG | Text | 10 | - |
| PSFLG | Text | 1 | - |
| PSDYR | Integer | 2 | - |
| PSDMN | Integer | 2 | - |
| PSDDY | Integer | 2 | - |
| PSDTM | Long | 4 | - |
| PSDUS | Text | 10 | - |
| PSDWS | Text | 10 | - |
| PSDPG | Text | 10 | - |
| NWFLG | Text | 1 | - |
| NWDYR | Integer | 2 | - |
| NWDMN | Integer | 2 | - |
| NWDDY | Integer | 2 | - |
| NWDTM | Long | 4 | - |
| NWDUS | Text | 10 | - |
| NWDWS | Text | 10 | - |
| NWDPG | Text | 10 | - |
| SBFLG | Text | 1 | - |
| SBDYR | Integer | 2 | - |
| SBDMN | Integer | 2 | - |
| SBDDY | Integer | 2 | - |
| SBDTM | Long | 4 | - |
| SBDUS | Text | 10 | - |
| SBDWS | Text | 10 | - |
| SBDPG | Text | 10 | - |
| EDFLG | Text | 1 | - |
| EDDYR | Integer | 2 | - |
| EDDMN | Integer | 2 | - |
| EDDDY | Integer | 2 | - |
| EDDTM | Long | 4 | - |
| IGFLG | Text | 1 | - |
| IGDYR | Integer | 2 | - |
| IGDMN | Integer | 2 | - |
| IGDDY | Integer | 2 | - |
| IGDTM | Long | 4 | - |
## Indexes
| Index Name | Fields | Primary Key | Unique |
|------------|--------|-------------|--------|
| RMSFILES#_EGSSL1A0 | +NEWPN | No | No |
| RMSFILES#_EGSSL1A1 | +CURPN | No | No |
| RMSFILES#_EGSSL1A2 | +CURPN | No | No |
| RMSFILES#_EGSSP1A0 | +CURPN | Yes | Yes |
## Usage
- Used by [[VBA_Scripts/Process_Sheet_Form]]
## Notes
- Auto-generated basic documentation due to Ollama unavailability. Check OllamaDebugLog.txt for details.
```yaml
---
tags: [Access, Manufacturing, Database]
created: 2025-06-13
---
```

43
Tables/RMSFILES__MFWKP795.md Normal file
View File

@ -0,0 +1,43 @@
# Access Table Documentation
# Access
# Manufacturing
# Database
## Overview
The 'RMSFILES#_MFWKP795' table is a crucial component of a manufacturing database, playing a vital role in managing parts and their corresponding details. This table serves as a repository for storing information about individual parts, including their sizes, weights, and material numbers.
## Fields
| Field Name | Type | Size | Description |
|------------|------|------|-------------|
| UID | Text | 10 | Unique identifier for each part, used to track and manage parts uniquely. |
| PRDNO | Text | 15 | Production number assigned to the part, often used in inventory management. |
| KBLWH | Text | 2 | Kilograms, but not necessarily weight (could represent other units). |
| SSIZE3 | Double | 8 | Size in inches for a specific dimension of the part (e.g., diameter, length). |
| BSIZE3 | Double | 8 | Base size or width of the part. Could be used to determine dimensions of cut components. |
| TSIZE3 | Double | 8 | Top size or height of the part. Used in conjunction with base and side measurements. |
| NETWT | Double | 8 | Net weight of the part, used in calculations related to inventory management and shipping. |
| GRSWT | Double | 8 | Gross weight of the part (including packaging). May be used for tracking shipping costs. |
| MATL# | Text | 15 | Material number assigned to the part, which can help identify its composition or intended use. |
## Indexes
| Index Name | Fields | Primary Key | Unique |
|------------|--------|-------------|--------|
| __uniqueindex | +UID | Yes | Yes |
| RMSFILES#_MFWKL795 | +UID;+PRDNO;+MATL# | No | No |
## Usage
This table is used extensively in the manufacturing database for various purposes, including:
- Inventory management: The UID field serves as a unique identifier for each part, allowing easy tracking and retrieval of inventory information.
- Part selection and ordering: By retrieving parts based on their UID or material number, manufacturers can efficiently select components for production.
- Shipping and cost estimation: The NETWT and GRSWT fields help calculate shipping costs accurately.
## Notes
- This table is designed to accommodate various part types and configurations, making it a versatile component of the manufacturing database.
- Regular updates and modifications to this table may be necessary as new part numbers or sizes are introduced, ensuring data accuracy and relevance.

101
VBA_Scripts/Process Sheet_Dependencies.md Normal file
View File

@ -0,0 +1,101 @@
# Process Sheet Dependencies
Analysis of tables, queries, modules, and reports used by the "Process Sheet" form, generated on 6/13/2025 4:05:22 PM.
## Record Source
- [[Queries/UniversalQ]] or [[Tables/UniversalQ]]
## Subforms
- Subform: Form1, RecordSource: [[Queries/AddnlQ1]]
- Subform: SubForm2, RecordSource: [[Queries/MachinesQ1]]
- Subform: PressBrakeSubForm, RecordSource: [[Queries/PressBrakeQ1]]
- Subform: PemPress Ops subform, RecordSource: [[Queries/SELECT DISTINCTROW [PemPress Ops].[PartNumber], [PemPress Ops].[OpCode], [PemPress Ops].[PemNumber], [PemPress Ops].[AutoManual], [PemPress Ops].[Hits] FROM [PemPress Ops];]]
## Control Sources
- Control: Field113, RowSource: [[Queries/SELECT metalQ1.MetalName, metalQ1.Gauge, metalQ1.PartNo, metalQ1.Length, metalQ1.Width, metalQ1.Density, metalQ1.Location, metalQ1.AltPartNo, metalQ1.PricePerLB, metalQ1.PurchaseBlank, metalQ1.WarehouseLocation, metalQ1.Units, metalQ1.[$NMWT] FROM metalQ1;]]
- Control: DatasheetFlag, RowSource: [[Queries/None;Req'd;All]]
- Control: Field325, RowSource: [[Queries/90;"Line Avenue";02;"Hollywood"]]
- Control: GrainDir, RowSource: [[Queries/No Grain Direction;Along First Dimension;Along Second Dimension]]
- Control: MetalType, RowSource: [[Queries/Select [MetalName],[Gauge],[PartNo],[WarehouseLocation] From [metalQ1];]]
- Control: CutType, RowSource: [[Queries/Single;Multiple;No CNC;Laser;Salvagnini;Blank;Laser/Shear;Single/Shear;Slug]]
- Control: Deburr, RowSource: [[Queries/Within;Outside;None]]
- Control: PressBrake, RowSource: [[Queries/PressBrakeQa]]
- Control: Field240, RowSource: [[Queries/Auto;Pedestal;Time Saver;Hand Deburr]]
- Control: SavedProcesses, RowSource: [[Queries/Select [WorkCenter],[Description],[WC1],[WC2],[WC3],[WC4],[CycleTime],[RunStd],[WCText] From [QWorkCenters];]]
- Control: PunchDie, RowSource: [[Queries/SELECT [PunchPress].[Die Number] AS Expr1, punchpressQ1.Location, punchpressQ1.IEDescription, punchpressQ1.Machine, punchpressQ1.[Safety Device], punchpressQ1.Comment FROM punchpressQ1;]]
## Tables
- [[Tables/MachineNames]]: Referenced in VBA (Set MachNamesSet = MachNamesDB.OpenRecordset("Mach...)
- [[Tables/Machines]]: Referenced in VBA (Set MachQSet = MachQDB.OpenRecordset("Machines", D...)
- [[Tables/Process]]: Referenced in VBA (Set MainSet = MainDB.OpenRecordset("Process", DB_O...)
- [[Tables/RMSFILES\#_EGSSP1A0]]: Referenced in VBA (Set XrefQSet = XrefQDB.OpenRecordset("RMSFILES#_EG...)
- [[Tables/RMSFILES\#_MFWKP795]]: Referenced in VBA (Set Main2Set = MainDB.OpenRecordset("RMSFILES#_MFW...)
## Queries
- [[Queries/UniversalQ]]: Form record source
- [[Queries/SELECT metalQ1.MetalName, metalQ1.Gauge, metalQ1.PartNo, metalQ1.Length, metalQ1.Width, metalQ1.Density, metalQ1.Location, metalQ1.AltPartNo, metalQ1.PricePerLB, metalQ1.PurchaseBlank, metalQ1.WarehouseLocation, metalQ1.Units, metalQ1.[$NMWT] FROM metalQ1;]]: Used in Field113 RowSource
- [[Queries/None;Req'd;All]]: Used in DatasheetFlag RowSource
- [[Queries/90;"Line Avenue";02;"Hollywood"]]: Used in Field325 RowSource
- [[Queries/No Grain Direction;Along First Dimension;Along Second Dimension]]: Used in GrainDir RowSource
- [[Queries/AddnlQ1]]: Subform Form1 record source
- [[Queries/Select [MetalName],[Gauge],[PartNo],[WarehouseLocation] From [metalQ1];]]: Used in MetalType RowSource
- [[Queries/Single;Multiple;No CNC;Laser;Salvagnini;Blank;Laser/Shear;Single/Shear;Slug]]: Used in CutType RowSource
- [[Queries/Within;Outside;None]]: Used in Deburr RowSource
- [[Queries/MachinesQ1]]: Subform SubForm2 record source
- [[Queries/PressBrakeQa]]: Used in PressBrake RowSource
- [[Queries/PressBrakeQ1]]: Subform PressBrakeSubForm record source
- [[Queries/Auto;Pedestal;Time Saver;Hand Deburr]]: Used in Field240 RowSource
- [[Queries/Select [WorkCenter],[Description],[WC1],[WC2],[WC3],[WC4],[CycleTime],[RunStd],[WCText] From [QWorkCenters];]]: Used in SavedProcesses RowSource
- [[Queries/SELECT [PunchPress].[Die Number] AS Expr1, punchpressQ1.Location, punchpressQ1.IEDescription, punchpressQ1.Machine, punchpressQ1.[Safety Device], punchpressQ1.Comment FROM punchpressQ1;]]: Used in PunchDie RowSource
- [[Queries/SELECT DISTINCTROW [PemPress Ops].[PartNumber], [PemPress Ops].[OpCode], [PemPress Ops].[PemNumber], [PemPress Ops].[AutoManual], [PemPress Ops].[Hits] FROM [PemPress Ops];]]: Subform PemPress Ops subform record source
- [[Queries/LogFileQ]]: Referenced in VBA (DoCmd.OpenQuery "LogFileQ", acViewNormal, acReadOn...)
## Reports
- [[Reports/Q1-14]]: Referenced in VBA (DoCmd.OpenReport DocName, A_PRINTALL, "Q1-14" + Ch...)
## Modules
- [[Modules/Form_Process Sheet]]: Form event handlers
- [[Modules/Custom_Functions#AddPartButton]]: Called in VBA (Call AddPartButton...)
- [[Modules/Custom_Functions#Add_Additional_Process]]: Called in VBA (Call Add_Additional_Process...)
- [[Modules/Custom_Functions#logFile]]: Called in VBA (Call logFile(currform!PartNumber, "Save As New Par...)
- [[Modules/Custom_Functions#HistoryR]]: Called in VBA (Call HistoryR...)
- [[Modules/Custom_Functions#Delete_Part]]: Called in VBA (Call Delete_Part...)
- [[Modules/Custom_Functions#Edit_The_Shear_Files]]: Called in VBA (Call Edit_The_Shear_Files...)
- [[Modules/Custom_Functions#Find_By_PartNumber]]: Called in VBA (Call Find_By_PartNumber...)
- [[Modules/Custom_Functions#Calculate_Button]]: Called in VBA (Call Calculate_Button...)
- [[Modules/Custom_Functions#GOTOPARTNUMBER]]: Called in VBA (Call GOTOPARTNUMBER(PN$, PrimaryScreen$)...)
- [[Modules/Custom_Functions#Button291_Click]]: Called in VBA (Call Button291_Click...)
- [[Modules/Custom_Functions#diskout]]: Called in VBA (Call diskout...)
- [[Modules/Custom_Functions#UpdateGWs]]: Called in VBA (Call UpdateGWs...)
- [[Modules/Custom_Functions#LaserTapeGenerate]]: Called in VBA (Call LaserTapeGenerate(p$, PaperFlag$, rst!)...)
- [[Modules/Custom_Functions#MoveFilesToPrefixLocation]]: Called in VBA (Call MoveFilesToPrefixLocation...)
- [[Modules/Custom_Functions#Button200_Click]]: Called in VBA (Call Button200_Click...)
- [[Modules/Custom_Functions#CalcCNCRunTimes]]: Called in VBA (Call CalcCNCRunTimes(p$)...)
- [[Modules/Custom_Functions#Button327_Click 'Laser Fun]]: Called in VBA (Call Button327_Click 'Laser Fun...)
- [[Modules/Custom_Functions#buttUpload_Click]]: Called in VBA (Call buttUpload_Click...)
- [[Modules/Custom_Functions#CutTypeFormSettings]]: Called in VBA (Call CutTypeFormSettings...)
- [[Modules/Custom_Functions#Find_By_MakeNumber]]: Called in VBA (Call Find_By_MakeNumber...)
- [[Modules/Custom_Functions#CrossRef]]: Called in VBA (Call CrossRef...)
- [[Modules/Custom_Functions#PBFormView]]: Called in VBA (Call PBFormView...)
- [[Modules/Custom_Functions#PemPressView]]: Called in VBA (Call PemPressView...)
- [[Modules/Custom_Functions#ErrorMessages]]: Called in VBA (Call ErrorMessages...)
- [[Modules/Custom_Functions#gatherinfo]]: Called in VBA (Call gatherinfo...)
## Notes for Obsidian
- **File Structure**: Store in `VBA_Scripts`, `Tables`, `Queries`, `Modules`, `Reports` folders.
- **Links**: Use [[Tables/TableName]], [[Queries/QueryName]], [[Modules/ModuleName]], [[Reports/ReportName]].
- **Special Characters**: `#` escaped as `\#` (e.g., [[Tables/RMSFILES\#_MFWKP795]]).
- **Tags**: `#VBA`, `#Access`, `#Manufacturing`.
- **Frontmatter**:
```yaml
---
tags: [VBA, Access, Manufacturing]
created: 2025-06-13
---
```