How to make database for billing system or inventory system

Question

0.00/5 (No votes)

See more:

I want to make a shop billing system or inventory system I am to much puzzled for database design i have made 3 tables in Access
1. Customer
2. Order
3. Product
please guide me .....
I am not leopard of C# therefore i dont want more table to manage. try to understand:-(

Posted 27-Nov-12 23:38pm

Muhamad Faizan Khan

Add a Solution

2 solutions

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)

__TR__ · Answer 1 · 2012-11-27T23:46:00

Solution 1

You might find the below link helpful
Library of Free Data Models[^]

Posted 27-Nov-12 23:46pm

__TR__

Pete O'Hanlon · Answer 2 · 2012-11-27T23:49:00

Your database design will be based entirely on the requirements of your client. You should be talking to them to find out what they want from the system. I will say that you are going to need more tables than that - unless you only allow a customer to place one order, and have one product. This means that you will need intermediate tables that map customers to orders, and orders to products.

As far as I can see, your question has very little to do with C#, and much more to do with the logical structuring of the database.