how to design Item Master Table Structure in inventory Management System

Question

1.00/5 (1 vote)

See more:

I want to design database for inventory management system which is small application .
In this situation i am confused with item master structure where need to create identity column or item number column which id will manually generated by using max(prev item number).
which approach is better.
From following design there is need to maintain itemno column or ID column is ok.
and also i want to know which approach is better and when to used.

ID ItemNo ItemName
28 000001 Visiting Card
29 000002 wedding card
30 000003 Company Letter
31 000004 Kids book

Posted 25-Jan-13 22:42pm

vishal_h

Updated 2-Aug-17 17:51pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mike Meinz · Answer 1 · 2013-01-26T01:56:00

Best Practice
Always design database tables with an Identity column that is hidden from the user and a visible identifier (Item Number, Item Code, etc.) that the user can see. Doing it this way lets you code your program so that the user can change the visible identifier without affecting the other tables that are linked to this table.

Also, users may tell you during design that they will never need to change the visible identifier. They will eventually have a situation where they have to change it. Whether it is a merger with another company or someone mistyped the identifier, there will be a need to change it. Designing the database tables following the above Best Practice makes life easier for you and your users.