How To Create A Sales Database?

[m0dd]

Anyone know how a sales database would be structured?
If anyone knows/has any exapmles of Microsoft Access Sales database, i would greatly apppreciate the kind gesture.

I understand that obviously Access wouldn't be used to build projects on that scale, but i'm not planning to create anything on that scale that will go live any time soon. However im assuming that the actaul structure wouldn't be to difficault to create on Access.

Thank you in advance.

 

[lomn75]

You're best off picking up a book on databases, as good design is beyond the scope of a forum thread.

 

[Kvothe]

You might also consider looking at Office Online as they have quite a few different templates available.

 

[m0dd]

is it that difficult? can't sum one just summarise the tables i need to create?

 

[SJConsultant]

No because you haven't provided any information as to:

1. what information you want to store.
2. What you want to be able to accomplish with that information.
3. How you want to retrieve the information.
4. What Reports you would like to generate based on the information.

This is only touching on basics needed to obtain a minimal idea of how the database would need to be constructed.

A sales database typically needs to be tailored to your specific needs and requirements, no one will be able to provide you with what you want until you provide a lot more information.

FYI, Microsoft provides a Northwinds sample database in MS Access format you should be able to derive some ideas.

 

[m0dd]

No because you haven't provided any information as to:

1. what information you want to store.
2. What you want to be able to accomplish with that information.
3. How you want to retrieve the information.
4. What Reports you would like to generate based on the information.

This is only touching on basics needed to obtain a minimal idea of how the database would need to be constructed.

A sales database typically needs to be tailored to your specific needs and requirements, no one will be able to provide you with what you want until you provide a lot more information.

FYI, Microsoft provides a Northwinds sample database in MS Access format you should be able to derive some ideas.

Many thanks for the insight.
Thanks for a very helpful reply.

The sample is very useful indeed, i maybe able to build my database based on it.

But for future reference for myself, you woulnd't mind being abit more specific about the points 2,3,4 you mentioned, i could sure use your expertise.

Is there any other questions i need to ask myself?
And if i provide answers to your questions, if it isnst to much trouble would you mind telling me what tables i need to create? I'll understand if you say no.

Sorry to hasssle you.
Many thanks again.

 

[SJConsultant]

Many thanks for the insight.
Thanks for a very helpful reply.

The sample is very useful indeed, i maybe able to build my database based on it.

But for future reference for myself, you woulnd't mind being abit more specific about the points 2,3,4 you mentioned, i could sure use your expertise.

Is there any other questions i need to ask myself?
And if i provide answers to your questions, if it isnst to much trouble would you mind telling me what tables i need to create? I'll understand if you say no.

Sorry to hasssle you.
Many thanks again.

I'll try to provide summary

1. what information you want to store.

You'll want to store the basic customer information such as name, address, telephone, fax, etc. but you need to ask yourself "What information do I want to store about my customers?" Many CRM (Customer Relationship Management) systems store information such as multiple contacts for the customer, birthdates, other important dates, notes, etc.

This only touches the surface of what information your storing *about* the customers, not knowing what business your in , or what your going to be "selling" those customers can dramatically change the landscape of what exact information is stored.

You need to sit down and document what you want to store about these customers. No one knows your customers or your business better than you.

2. What you want to be able to accomplish with that information.

Ask yourself, "Why am I storing this information?" Eventually you'll want to retrieve that information and do something with it. Some businesses use it to track sales, invoiceing, marketing, etc.

Again your business will dictate what exactly you will be doing with that information.

3. How you want to retrieve the information.

There are many choices in databases out there, and as such, you need to figure out what will work best in your situation.

Will this be a single or multiuser DB?
Will the database need to be portable or can it stay at the office?
Will you need to access the DB from a remote location?
What information do you want displayed when you retrieve customer information?


4. What Reports you would like to generate based on the information.

Reports are going to be based on your business, what you sell, and your customers. Typically reports can be as simple as a sales summary, marketing label list, or outstanding invoices.

The important thing to remember is that anytime your pulling the same information on a regular basis, it should be made into a report for simple retrieval.

As you start answering these questions above, you'll notice that you are starting to build the "tables" yourself for the database. I couldn't possibly provide a set of tables based on the information provided so far. It would take an intense evaluation of your business, customers, business issues, and why you want a database in the first place.

There are other factors in building a database that need to be addressed before you even begin. First of which is how the information is going to relate. Although you can build a database with a single table, it's not going to be very useful or easy to administer.

It sounds like you've never built a DB before and honestly, I would recommend picking up a few books on the subject before attempting to build it.

 

[rebelleader]

If you have MS Access installed try taking a look at the sample database called Northwind. It is included with the install. It is a sample database that may be able to help you out.

 

[m0dd]

I'll try to provide summary

1. what information you want to store.

You'll want to store the basic customer information such as name, address, telephone, fax, etc. but you need to ask yourself "What information do I want to store about my customers?" Many CRM (Customer Relationship Management) systems store information such as multiple contacts for the customer, birthdates, other important dates, notes, etc.

This only touches the surface of what information your storing *about* the customers, not knowing what business your in , or what your going to be "selling" those customers can dramatically change the landscape of what exact information is stored.

You need to sit down and document what you want to store about these customers. No one knows your customers or your business better than you.

2. What you want to be able to accomplish with that information.

Ask yourself, "Why am I storing this information?" Eventually you'll want to retrieve that information and do something with it. Some businesses use it to track sales, invoiceing, marketing, etc.

Again your business will dictate what exactly you will be doing with that information.

3. How you want to retrieve the information.

There are many choices in databases out there, and as such, you need to figure out what will work best in your situation.

Will this be a single or multiuser DB?
Will the database need to be portable or can it stay at the office?
Will you need to access the DB from a remote location?
What information do you want displayed when you retrieve customer information?


4. What Reports you would like to generate based on the information.

Reports are going to be based on your business, what you sell, and your customers. Typically reports can be as simple as a sales summary, marketing label list, or outstanding invoices.

The important thing to remember is that anytime your pulling the same information on a regular basis, it should be made into a report for simple retrieval.

As you start answering these questions above, you'll notice that you are starting to build the "tables" yourself for the database. I couldn't possibly provide a set of tables based on the information provided so far. It would take an intense evaluation of your business, customers, business issues, and why you want a database in the first place.

There are other factors in building a database that need to be addressed before you even begin. First of which is how the information is going to relate. Although you can build a database with a single table, it's not going to be very useful or easy to administer.

It sounds like you've never built a DB before and honestly, I would recommend picking up a few books on the subject before attempting to build it.

Firstly apologise for my late reply.
I wanted to experiment first, instead of having to always come crying back for help.

Second i can't express my gratitude to you, thank you m8 .

My reason for posting is i will be absent from this thread for a while and didn't want to leave you hanging. Im getting the into this project, and think i should carry on alone as i don't want to always hassle you m8. But your summary and espically the sample database you provided is amazingly helpful.

But rest assured, I will be back when i get stuck