What is my next step?

  • Thread starter Thread starter Angie
  • Start date Start date
A

Angie

1st, thanks for taking the time. I appreciate it.

I am trying to build a database. I have my tables made, and I know how I
want it to work, but I don't know how to go about it.

1. I want it to automatically bring up the name of the line in the next
feild when they put the line no. in the previous feild.

2. I need to have the option of more than one selection in a feild.
Example: They worked on a line and had to both cut down a tree, and spray for
weeds.


There is so much that I don't know how to do in Access. I have never needed
to build this kind of database. It is complex. I may not even be going about
it the right way.

Overall outcome wanted:

-Be able to search a pole number on a specific line and have it bring up all
previous work associated with that pole and the area arround it.

-Also need to log daily work reports, which will reference multiple poles
and the work they did to the area, into that database so that it can be
easily pulled up when doing the search above.

-Factors in the general db: Line No., Line Name, Inspector/workmans name,
date of inspection, date of completion, what was done, clasification of work,
priority of work needed, man hour spent on the task, other coments.

I need to be able to pull up records by referencing any one of the feilds.
It also needs to be very simple to understand. Most of the men who will be
putting their daily tasks into the database are not good with computers.

***Am I in over my head? Should this be something that a professional needs
to design?
 
Responses inline.

Angie said:
1st, thanks for taking the time. I appreciate it.

I am trying to build a database. I have my tables made, and I know how I
want it to work, but I don't know how to go about it.
Click to expand...
We don't know how it needs to work, so some details about the structure
would help people in the newsgroup provide specific suggestions.
1. I want it to automatically bring up the name of the line in the next
feild when they put the line no. in the previous feild.
Click to expand...
You can do this, but you will need to describe how it happens that the line
number and the line name are connected. Is there a Line table?
2. I need to have the option of more than one selection in a feild.
Example: They worked on a line and had to both cut down a tree, and spray
for
weeds.
Click to expand...
This calls for a related table for TasksPerformed. It sounds as if you will
also need a table for Maintenance (or something). It sounds as if each line
would be its own record (LineNumber, LineName, LineLocation, etc.). Each
maintenance job would be related to a line, and each task performed would be
related to the maintenance job. Again, details of the structure are needed.
 
Ok, this is the table they are working with now:


Line_No Line_Name Inspector_Name Inspection_Date Start_Pole_No
10-A BARKLEY - SIPCO RANDALL 10-Mar-08 95
10-A BARKLEY - SIPCO RANDALL 13-Mar-08 92
10-A BARKLEY - SIPCO RANDALL 12-Mar-08 95

....End_Pole_No RW_Width Sprayed Cut Full_Width Priority Phase
96 125 FALSE TRUE FALSE P2-B 1
94 FALSE TRUE FALSE P3-B 2
96 FALSE TRUE FALSE P4-B 1

....Hours MoreToDO Completed Paperwork Remarks
10 TRUE FALSE TRUE REMOVED 3 TREES, WIDENED R/W **MORE TO DO**
10 TRUE FALSE TRUE REMOVED 2 TREES ON EDGE OF R/W **MORE TO DO**
5 FALSE TRUE TRUE REMOVED 3 TREES, WIDEN R/W


BruceM said:
Responses inline.


We don't know how it needs to work, so some details about the structure
would help people in the newsgroup provide specific suggestions.

You can do this, but you will need to describe how it happens that the line
number and the line name are connected. Is there a Line table?
Click to expand...

yes there is a line table. Looks like this (with 200 rows)

LineNumber LineName
10-A Barkley - Ohio River Crossing
10-B Livingston Co. - McCracken Co.
10-C "McCracken Co. - TVA Line ""L"""
10-D Marshall Tap Line
11-A Union Star - Andyville
This calls for a related table for TasksPerformed. It sounds as if you will
also need a table for Maintenance (or something). It sounds as if each line
would be its own record (LineNumber, LineName, LineLocation, etc.). Each
maintenance job would be related to a line, and each task performed would be
related to the maintenance job. Again, details of the structure are needed.
Click to expand...

Background info: I am talking about powerline poles and the maintenance they
do to them, and the hazardous trees and enviornment arround them.

Well, each task (sut, spray...) is related to a Problem (Leaning tree,
burning tree,...), which is the maintenence job. Each job is associated with
a group of poles (Starting Pole No, THROUGH Ending Pole No.) on a line.
Incomplete jobs are done in order of Priority. and need to be marked as to
whether it is fully complete, or if there is more to do. As well as other
important comments.

The tables I have set up are:
Action Taken (Spray, Cut, Inspect...)
Problem Type (Leaning Tree, Dead Tree, Fallen Tree...)
Qty (number of trees)
Inspector name (Names and Employee numbers)
Line Name-No
Phase (1 or 2)
Pole No (1-300) **Will I need to break down each line into a list of poles?
I hope not
Priority (P2-B, P3-B...)


I hope that is enough information, if not, please let me know.
 
You have described your tables, but not how they are related to each other.
It seems the top level is the Lines table:

tblLine
LineID (primary key - could be autonumber, or your assigned number if
that will never change. If there is a chance it would change I would
suggest autonumber)
Line_No
Line_Name

tblInspector
InspectorID (primary key, or PK)
FirstName
LastName

tblInspection
InspectionID (PK)
InspectorID (related to tblInspector)
LineID (related to tblLine)
InspectionDate

tblInspectionFinding
FindingID (PK)
InspectionID (related to tblInspection)
Finding (leaning tree, etc.)

tblRepair
RepairID (PK)
LineID
RepairAction (cut tree, etc.)

The Findings table and the RepairAction table could be lookup tables that
are used to insert a value into tblInspectionFinding and tblRepair if the
finding or action is a single field such as "leaning tree" or "cut tree".

There are more angles to this. For instance, if each inspector can inspect
many lines, and each line may be inspected by one of several inspectors,
another table is needed to resolve the many-to-many relationship.

I would suggest some reading to learn more about how all of the parts go
together. This link:
http://allenbrowne.com/tips.html
contains a tutorial and other links in Tips for Casual Users, plus a Links
link on the right side of the page.

That's all I can add just now.
 
Back
Top