- Sep 27, 2002
- 6,209
- 1
- 0
I'm an on-scene rep for an engineering company providing technical oversight and my job involves reviewing procedures, component discrepency reports, along with passing trouble records back to the engineers at our lab to resolve.
Right now we track everything in an Excel spreadsheet, which certainly has its drawbacks, such as its inability to query and generate reports. I've got some downtime for the next couple of months, so I've decided to create a database that will track these things more efficiently.
Is MS Access the right tool to use? Can anyone recommend a web site or book(s) that could help me understand DB design so I can put this together right? I've been able to get the basic concept from some Google searching, but nothing seems to give me enough depth to build something I'd actually want to use.
Right now we track everything in an Excel spreadsheet, which certainly has its drawbacks, such as its inability to query and generate reports. I've got some downtime for the next couple of months, so I've decided to create a database that will track these things more efficiently.
Is MS Access the right tool to use? Can anyone recommend a web site or book(s) that could help me understand DB design so I can put this together right? I've been able to get the basic concept from some Google searching, but nothing seems to give me enough depth to build something I'd actually want to use.