Database to Track Work?

[Hakala]

Hi, everyone!

I'm looking at redesigning the "Tracking" database we have in our office. Currently, it tracks incoming receipts, who has them, current status, a bunch of dates, and some other related items. If a full list would be helpful, I can post it.

I'm looking for ideas on the "perfect" tracking system. If anybody has tips or examples, please let me know?

 

[lespaul]

I would recommend that you read the fundamentals document below to help design the table structure. After that, if you have some specific questions, we'll try to help out and once you have a basic outline of your tables, we'll be happy to critique it for you too!

Leslie

Anything worth doing is a lot more difficult than it's worth - Unknown Induhvidual

Essential reading for anyone working with databases: The Fundamentals of Relational Database Design

 

[jrbarnett]

The perfect tracking system (for you) is one that meets your needs. If you need it just to track IT support calls, for example, you will need a different structure for those that need to store details of programming jobs as well, do you need your users to be able to submit jobs themselves via an application etc.

As lespaul says, if you can give us examples of your current structure design and requirements, we can help you further.

John

 

[ceh4702]

Track what work?

Is this a Production Workflow for producing products from raw materials??

Inventory Mangement?

Sales?

Service?

Today it seems like everyone wants a custom solution for a unique business model. Have to define the business model first.

If you do not like my post feel free to point out your opinion or my errors.