homepage Welcome to WebmasterWorld Guest from 54.224.79.93
register, login, search, subscribe, help, library, PubCon, announcements, recent posts, open posts,
Accredited PayPal World Seller

Visit PubCon.com
Home / Forums Index / Code, Content, and Presentation / Databases
Forum Library : Charter : Moderators: physics & whoisgregg

Databases Forum

    
A pointer for Access please
Trying to develop an Access DB for Ebay
douger9999




msg:1579565		 11:33 am on Oct 12, 2005 (gmt 0)

Hello all,

I am trying to develop an Access DB for items I've bought and sold on Ebay. I am however trying to start using a normalised format - as I want to do the job properly.

1) Does anyone know of any tutorials which would help me?

2) I just thought I'd run something by you re the relations of my tables.

I have at the moment 3 tables
- Name
NameID,EbayID,First_Name,Second_Name,
1,chuckster,Chuck,Wormington
2,Jakester,Jacob,Fotheringay
etc...

- Item
ItemID,Description
1,Washing Wachine
2,Scooter
etc...

- Deals
dealID,ItemID,SellerID,PurchaserID
1,1,1,2
2,1,2,1
etc...

My relationships are
Itemid(items) -> Itemid(deals)
nameid(name) -> Sellerid(deals)
nameid(name) -> Buyerid(Deals)

Am I going about this the right way?

Any help greatly received.

Thanks

Doug

 

aspdaddy




msg:1579566		 6:26 pm on Oct 13, 2005 (gmt 0)

Looks ok, I would add date, price and transaction type to deals though. Transaction type could be a bit,0=sale,1=buy.

HTH

douger9999




msg:1579567		 8:51 pm on Oct 13, 2005 (gmt 0)

Thanks ASPDADDY,

I am trying to keep it simple to begin with, as it's my first serious DB. I was going to add all of the other fields later 'Buy it now?' 'price' 'delivery cost' etc etc.

I am really looking for tutorials etc to begin with...

thanks

Doug

aspdaddy




msg:1579568		 10:53 am on Oct 14, 2005 (gmt 0)

You wont find many tutorials of use on data modelling, the best way to learn is by experience. At least (looking at your fist attempt). you seem to understand the concept of normalisation very well. Its a way of thinkin about data that you either get it or you dont.

Just cary on & keep test the designs by how easy it is to construct Insert, Update, Select queries, including reports and how easy it is to extend the model, import and export data.

Think long term and try come up with possible ways to get incorrect data in te dataabse i.e bulk upload, delteing related records using code to enfore rules instead of the database or by mistakes in data enty. All these test the design for 'fit for purpose'-ness much better than following tutorials on the theory of how to do it.

HTH


nameid(name) -> Sellerid(deals)
nameid(name) -> Buyerid(Deals)

Two roles on the same table! Maybe rename the table BuyersAndSellers, Names is a bad name! When you make Views try to remove one of these relations or you can get a bit of a mess.

Global Options:
 top home search open messages active posts  
 

Home / Forums Index / Code, Content, and Presentation / Databases
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About
WebmasterWorld ® and PubCon ® are a Registered Trademarks of Pubcon Inc.
© Pubcon Inc. 1996-2012 all rights reserved