Question Database structure.

[HenricB]

Hello there Masters of Access.

Im new to this wonderful forum which has helped me alot to solve many questions. Just love it!

My question is of the nature that might fall into many categories so i placed it under General, I appologise if it happens to be under the wrong subject.

I am building an inventory control database where I can have the same article number (not the article itself) on five different places and I want to make orders and update the database. So my question to you guys are:
What apporach is best;
1. Having one database where I specify where the article is located. (This makes the updating on the database with new prices and even new articles harder. I have to for eg. write Company name, deliverytime, product name five times. I have not even begun to imagine when I start working on the ordering part.).
2. Having five separate databases for every location. (That makes everything a bit easier but the big problem is where I want an overview of what I have in total of that article number)

This might be a very challenging question to answer but I am all alone on this matter. My friends and family are not remotest interested in my questions. I have a few books that I have read but it does not make anything clearer for me.

Best regards
Henric

 

[pl456]

You say you will need to enter the article with prices etc five times, you would need to do that if you had five databases so there is no gain or lose in the amount of data entry.
Administrating 1 database is by far so much easier especially if you modify tables, queries, forms ect you don't want to be doing that five times.
So I suggest 1 database.

 

[Guus2005]

My friends and family are not remotest interested in my questions.

Have no fear: Guus is here!!

Define places. Same network?
Did you split the database in a frontend and a backend?

 

[MSAccessRookie]

Hello there Masters of Access.

Im new to this wonderful forum which has helped me alot to solve many questions. Just love it!

My question is of the nature that might fall into many categories so i placed it under General, I appologise if it happens to be under the wrong subject.

I am building an inventory control database where I can have the same article number (not the article itself) on five different places and I want to make orders and update the database. So my question to you guys are:
What apporach is best;
1. Having one database where I specify where the article is located. (This makes the updating on the database with new prices and even new articles harder. I have to for eg. write Company name, deliverytime, product name five times. I have not even begun to imagine when I start working on the ordering part.).
2. Having five separate databases for every location. (That makes everything a bit easier but the big problem is where I want an overview of what I have in total of that article number)

This might be a very challenging question to answer but I am all alone on this matter. My friends and family are not remotest interested in my questions. I have a few books that I have read but it does not make anything clearer for me.

Best regards
Henric

Henric,

When I started programming in Access, I was somewhat overwhelmed too. One thing that I quickly discovered was that this group is very supportive of its members, and I imagine that it will not be too long until you (as I have) are willing and able to return the favor by assisting the next group of new people. In the mean time, feel free to ask any questions and we will try to reply.

For your own purposes, you can obtain and read All the access books you want, but nothing is better than trying it out for yourself. The Link below points to One of the many FREE Online MS Access Training Options. Each class usually takes between 20 minutes and an hour to complete, and most are well worth their time to a new MS Access user.

http://office.microsoft.com/en-us/training/default.aspx

 

[HenricB]

Good morning everyone!

Back at work and ready to get going with new fresh energy! Can say that I were a bit low yesterday. With your responses I definetly feel that this database will see its dawn! Thanks alot for replying.

I will go for 1 database as you suggest pl456 as new to this thing it can be hard to forsee the obstacles that might arise further ahead.

Guus2005! I will now sleep well at night =)
The only one to administer this database is me and my boss. There is no need to put it on the network. But it can be a good idea to think of in regards of future needs. So there is no need for a backend and a frontend...yet =) But is there anything I should think of for future needs when forming this database if there would arise such a request for mulitple users?

MSAccessRookie, thanks for kepping my spirit up. This whole database thing does indeed very overwhelming. With you guys (and I will try not to ask about every single obstacle that I may encounter =) ) this project seems very doable. The link you gave me is very very nice. I never saw that training program only the help section at microsofts site. Thanks! Going to be a fun day this =D

Thanks alot once more for your replies!
HenricB