Results 1 to 3 of 3
  1. #1
    cmb is offline Novice
    Windows 7 64bit Access 2013
    Join Date
    Sep 2014
    Posts
    11

    Advice on designing my 1st database

    Hi there,

    I'm building my first database and think the following design would work but I would like any feedback or advice before I proceed. The purpose of the database is to schedule an installation technician (FSE) and application specialist (APPS) to install equipment at a customer site and train them. An order comes in, which may have been sold by a dealer, it is assigned to a technician and an application specialist and a separate appointment needs to be made for each. Ultimately, this will be viewed as a calender as a form.

    Many thanks in advance!
    Click image for larger version. 

Name:	DB.jpg 
Views:	26 
Size:	94.0 KB 
ID:	18071

    Attached Files Attached Files

  2. #2
    ItsMe's Avatar
    ItsMe is offline Sometimes Helpful
    Windows 7 64bit Access 2010 32bit
    Join Date
    Aug 2013
    Posts
    7,862
    The first diagram looks good. I can't see the second picture. tblOrders has AppointID and I suppose this is not needed. You may consider additional tables related to your tblOrders in order to support operations. Maybe not have tblAppoints so complex and move some of those fields into new, child, tables of tblOrders. Maybe have tblAppoints relate to these new tables instead of it relating to tblOrders.

  3. #3
    ssanfu is offline Master of Nothing
    Windows XP Access 2000
    Join Date
    Sep 2010
    Location
    Anchorage, Alaska, USA
    Posts
    9,664
    Don't need "AppointID" in table "tblOrders". One order can have many appointments, one appointment can have one order. "OrderID" is the linking field.

    Why not combine the tables "tblFSEs" and "tblAPPs" into "tblVendors" or "tblTechs"? Add a field for "TechType" (FSE or APP).
    I also like having a first name field and a last name field for people (not businesses).


    it is assigned to a technician and an application specialist and a separate appointment needs to be made for each
    If this means the two techs have different appointments scheduled, you might want to change the structure a little:

    in tblAppoints, change:

    "FSEvenderID" to "VenderID"

    "APPSvenderID" to "VenderTypeID"


    tblVendorTypes
    VenderTypeID(Autonumber - PK)
    VenDesc (Test)

    Data: "FSE", "APP"




    (See spreadsheet)


    My $0.02

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Need help and advice designing a call center database.
    By AbandonedRobot in forum Database Design
    Replies: 3
    Last Post: 07-20-2014, 01:49 PM
  2. database designing
    By tommyried in forum Database Design
    Replies: 1
    Last Post: 02-27-2014, 12:41 PM
  3. Designing my database
    By ldypurple in forum Database Design
    Replies: 11
    Last Post: 03-06-2013, 10:58 PM
  4. Designing a database for a log
    By neo651 in forum Database Design
    Replies: 3
    Last Post: 10-31-2011, 11:45 AM
  5. Help with designing database
    By nimalp in forum Access
    Replies: 6
    Last Post: 09-15-2010, 10:34 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums