Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2004
    Alpine Califormia

    Unanswered: a one to many relationship for vendors and vendor dues (was "Help")

    I need to create a database for another department Access xp will of course be the Gui and SQL server 2000 as the Engine. Its a Vendors database one table should show the Vendors Information the name of the company vendorID, etc. The other table will show the Vendor Dues this table will consist of VendorId the duesID (need a unique number for it though this table will need to be updated also) the check#, the creditamount, debitamount,code, and date paid. Was thinking of making a one to many relationship there. But I would like to get the experts opinion. Both tables will need to be updated

    Any Ideas Honorable Gurus

  2. #2
    Join Date
    Apr 2002
    Toronto, Canada
    please try to use more descriptive subjects than "Help" | @rudydotca
    Buy my SitePoint book: Simply SQL

  3. #3
    Join Date
    Jun 2003
    Your approach seems fine to me. One table has the Vendor information with VendorId as the PK and Dues table with DueId as the PK and VendorId as the FK from Vendor.

Posting Permissions

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