Results 1 to 6 of 6
  1. #1
    Join Date
    Aug 2009
    Posts
    18

    Unhappy Unanswered: Need help with relationshiop tables please

    The system i am trying to create is a warehouse type system where suppliers details are kept along with the products they are supplying. And at same time keep records of the purchasers (customer) details and the products they have bought.

    The tables created are

    *ClienBuyerDetails (customer details)
    *ClientSuppliersDetails(SupplierDetails)
    *Products (supertype)
    *Laptop (subtype)
    *PC (subtype)
    *Printer (subtype)
    *TFT (subtype)
    *generalwaste

    The suppliers will be supplying laptop,pc,printer , tft and customer will purchase the products.

    Im lost with the relationship tables and i dont know if they are linked correctly. I am not sure weather im missing a table or if my relationships are incorrect.

    I would love to and other details regarding tax and dates etc, but not quite sure how to do it. Also thought i would need a method of payment select i.e visa, cash, debit. I have added several table, is this correct?

    I want make one simple database for suppliers details and products their supplying and customer purchasing the products. And then later will improve database including payment methods, tax etc. At moment i want a simple type database. I have attached 2 relation ship tables one simple and one with tax, payment method etc.
    Attached Thumbnails Attached Thumbnails relationships deleted asscociation tables.JPG   database relationships deleted association tables and added new tbales.JPG  

  2. #2
    Join Date
    Aug 2009
    Posts
    18
    anyone please help me.

  3. #3
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Don't have the time to help a lot, but here's a tip you can fix up some stuff:

    Get rid of spaces and question marks and any other weird characters from your field and table names.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  4. #4
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    And correct spelling too... "mobikle number"?? "Clienbt surname"??

    A little care in table design will save a lot of stress later on.

    I wish I could help more,... your table design needs a considerable amount of work to fix.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  5. #5
    Join Date
    Aug 2009
    Posts
    18
    hi, thank you for the advice. I think i was putting 100% into the relationships of the tables and forgot about the odd characters and spaces in my tables, thank you.

    I am still lost with the relationships of the database, could anyone please be of assistance. I want to concentrate on the simple database which i have attached the picture on the left of the relationships. The other database (attachment of pic on right) is more complicated and deals with tax, method of payment, and discount etc which is more complicated, which is why i don't want to concentrate on this at the moment. My focus is on the simple database so i can actually start to my data, later i will then update and improve the database to include the more complicated information.


    Thank you for help i appreciate it

  6. #6
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Where to start....

    * Employers don't have products?
    * Each PKF should be the ID of the table, you seem to have too many ProductIDs. EG: a Printer table should have PrinterID, not a ProductID.
    * The multiple 1:1 relationships at the left all seem to me to be wrong. With your current design, the following statements are true: each product has a laptop (sounds very wrong to me already) and each laptop has a product. Each product has a printer and each printer has a product. Each product has a PC and each PC has a product. Sounds very wrong to me.
    * Most of the rest is dependant upon the business model - what your goals are determine whether or not the rest of your fields are correctly placed or not.

    If I were you, I would hire a consultant for an hour or two to go over table design. Getting tables right is critical and you should be in NO hurry to get to enter data. Rush your tables, rush to your data entry (save yourself 10 hours) and you will pay the price many times over -- spending 100's of hours fixing stuff and re-developing forms you have already "finished"!
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •