Is acces what I need

[jammerculture]

I have this idea for a computer program that will make my job as an electrical foreman much easier. I'm pretty sure that I can use Access for what I want but don't know, so I need some advice.



Currently we use Excel tables for everything, timesheets, order forms, tracking. I want to move everything into Access for a few reasons. On the material front our current system of Excel table order forms creates two main problems. There is a lot of duplicated data, and time wasted duplicating it. For example if I order 300' of 3" EMT conduit, I need to order straps and connectors and couplings so I type out 3" EMT connectors x 10, 3" EMT couplings x 50, 3" EMT straps x 100. This process is repeated when I order 1/2" EMT or 3" PVC. I think it would be easier to store the material info and then have a form with drop down menus for size, type etc. I ideally I would like to be prompted for the accessories once conduit is chosen, or connectors when cable chosen, this kind of functionality. I would also like to know how much 3" EMT I have used in the last year or five or month.

Also when two applications use the same material I would like the program to be able to deal with totals. Ideally I would like something that I could define specific tasks on the job. At the design phase of the project each job would get a take off for time and material. Later I could order material by job and call the take off that was created at the design phase and a report would be generated and sent to the purchasing agent.

I would also like to be able to store my workers, and assign workers to these specific tasks as they come up, hopefully using outlook calendar and contact functions. Currently worker payroll is done using excel tables of hours, based on days of the week, which are emailed to the main office from site. I would like to be able to do payroll based on these job ID's and be able to monitor estimated time in relation to actual time.

I would also like the program to be able to keep a portfolio of the employees, the specific tasks they have accomplished, and some form of ratings for efficiency in time and material. As apprentices it is important that the guys get a broad base of experience throughout their apprenticeships and a system like this would go along way to helping us develop the guys to their fullest as they move from foreman to foreman. At it's largest extreme, I would like something that the owner could use to keep tabs on all the jobs, aggregate material over the course of the year to allow for larger purchases, and be able to rate the merits of the different approaches taken by the various foremen working for him.

I would really really appreciate some advice form those of you who know how to utilize this stuff to its fullest as my experience and knowledge is above average but lacking. I need to know what I need to learn so I can get on it. Thanks for all the help you can give me.

[June7]

Relational database is intended for this kind of application, however, the database types you need are among the more difficult to create: manufacturing (product assembly) and payroll. Both have been discussed in forum numerous times. Search those topics here and Google.

Here is one on manufacturing to review https://www.accessforums.net/access/...her-28286.html

There are databases out there for this but they probably have purchase cost, not much in the way of freebies in those areas.

[jammerculture]

thanks for the response. I will check out the thread you linked to. I am really looking forward to making the database myself, I have always found this type of work interesting. I know I will have to learn a lot in order to make something as complex as I envision, so I want to make sure that the skills I learn and the avenues of learning I pursue are the correct ones for what I want.

[E. Rumsey]

I second June7's comment that Access is an appropriate tool for what you're trying to do. It does seem like it will take you a while to build up the many components of the database you will ideally have eventually, but some of the functions you mentioned are a lot easier to create than manufacturing and payroll (for example order tracking), so the database will start being helpful even if you don't have the expertise to build the more involved stuff right away.

[jammerculture]

I am taking your advice to break the database into its simpler functions and work on them individually. I have created a thread https://www.accessforums.net/access/...orm-29843.html that addresses the specific order tracking aspect.

[E. Rumsey]

Best of luck!