Iam working on a purchase managment system that manages the puchases and inventory of the company that sells pcs. i want to manage employees (pemant,consultants) , customers , supliers , business partners all will be the users in the application . what would be the right design of the database should i create all of them in saparate entity or what would be right design .???
Regards
Adeel
Jump to PostIts really very difficult to suggest from here without having the knowlwdge of actual requirment at your side.
I would suggest you instead of storing them separately ,store with some flag setting as a single entity.
Its really very difficult to suggest from here without having the knowlwdge of actual requirment at your side.
I would suggest you instead of storing them separately ,store with some flag setting as a single entity.
agreed.
the idea of a relational database is to vastly reduce the amount of stored data by keeping it separate and unique.
get a copy of microsoft access (even a very old copy) and look at the north wind traders database. it is what you describe.
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.