访问审计检查+历史封锁!

发布于 2024-10-08 00:06:54 字数 1233 浏览 3 评论 0原文

目标:

- electronic form which displays 45 inspection points (rarely changes)
- 3 additional columns
  - Rating (0, 1, 2)
  - CorrectiveAction (Immediate, SOP, WO)
  - Notes
- Maintain inspection history
  - inspection date, production line inspected, production shift-crew inspected

表格:

- Employee (empID (auto#), FName, LName, Shift, Line)
- Audit Facts (ID#, textdescrip)   tried with and without autonumber
- Audit Details (auditID (auto#), auditdate, rating, action, notes)  *(rating/action combobox)

表单中的子表单具有 45 个检查点,全部与审核编号相关联。但是,我无法将审计结果记录、存储并移入历史。

我所做的每一次尝试都会在每 45 个检查点生成一个审核编号,而不是

 Audit Date
   AuditID(auto#)
      AuditFact (list of 45 chckpts)

结果

        Audit1, 10/02/2010 ->
           *AuditPt     Rate     Action*        
                IF1          0      WO
                IF2          2      SOP
                ... 
                IF45         1      Immediate

        Audit2, 12/15/2010 ->
           *AuditPt     Rate     Action*        
                IF1          1      WO
                IF2          0      SOP
                ... 
                IF45         0      Immediate

Objective:

- electronic form which displays 45 inspection points (rarely changes)
- 3 additional columns
  - Rating (0, 1, 2)
  - CorrectiveAction (Immediate, SOP, WO)
  - Notes
- Maintain inspection history
  - inspection date, production line inspected, production shift-crew inspected

Tables:

- Employee (empID (auto#), FName, LName, Shift, Line)
- Audit Facts (ID#, textdescrip)   tried with and without autonumber
- Audit Details (auditID (auto#), auditdate, rating, action, notes)  *(rating/action combobox)

A subform in a form has the 45 check points all tied to the Audit number. However, I cannot get the audit results to record, store and move into history.

every attempt i've made produces an audit number PER each 45 checkpts, as opposed to

 Audit Date
   AuditID(auto#)
      AuditFact (list of 45 chckpts)

results

        Audit1, 10/02/2010 ->
           *AuditPt     Rate     Action*        
                IF1          0      WO
                IF2          2      SOP
                ... 
                IF45         1      Immediate

        Audit2, 12/15/2010 ->
           *AuditPt     Rate     Action*        
                IF1          1      WO
                IF2          0      SOP
                ... 
                IF45         0      Immediate

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

任谁 2024-10-15 00:06:54

把你的桌子摆好&您的表格将随之而来。

最初的问题并不完全清楚,但我认为我得到了这些要点:

  1. “审核”与“检查”相同
  2. 集合 45个“检查点” ”构成一项审计(不是每一项单独审计)。
  3. “评级”和“行动”适用于每个检查点。

因此,您的表希望更像这样:

Audit
  AuditId (can be autonumber, or not...)
  AuditDate

AuditItem
  AuditItemId (can be autonumber, or not...)
  AuditId (FK from Audit)
  InspPoint (e.g., the "IF1" from the "result" sample, or--better--an FK to it another table)
  Rating
  Action (Or--better--an FK to it another table)

表“Employee”似乎与此结构完全无关。

请注意,每个剖切点在 AuditItem 中都有自己的行,针对每个审计,并且这些行还带有来自 Audit 的 AuditID,这使您可以将它们全部放在一起进行输出。

希望这有意义 - 如果没有,我建议您查看基本关系数据库设计

Get your tables right & your forms will follow.

The original question isn't entirely clear, but I think I got these points:

  1. An "Audit" is the same as an "Inspection"
  2. The collection of 45 "inspection points" constitutes an Audit (not each one individually).
  3. "Ratings" and "Actions" apply to each inspeciton point.

So your tables want to be more like this:

Audit
  AuditId (can be autonumber, or not...)
  AuditDate

AuditItem
  AuditItemId (can be autonumber, or not...)
  AuditId (FK from Audit)
  InspPoint (e.g., the "IF1" from the "result" sample, or--better--an FK to it another table)
  Rating
  Action (Or--better--an FK to it another table)

Table "Employee" seems entirely irrelevant to this strucure.

Note that each Insection Point has its own row in AuditItem, for each Audit, and that those rows also carry the AuditID from Audit, which lets you pull them all together to make you output.

Hopefully this will make sense--if it doesn't, I recommend reviewing fundamental relational database design.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文