Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2010
    Posts
    1

    Unanswered: complex design assistance needed!

    Hi everyone.

    I am currently designing a database for a content management system. The idea is the administrator can pick from a drop down menu a 'module'. Now this module could be a contact form, a html section or anything like that. The point here is each module will have different config fields. For example, a contact form might have send to, send from, subject etc whereas the HTML seciton might have content, title, publish date and so on. Each page can have more than 1 section on it. I originally thought I could have a modulesforpage table, but as each module will have different columns that would not work.

    My question is, how can i structure this in the database?

    Any advise would be great!

    Thanks.

  2. #2
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,424
    Provided Answers: 8
    idea
    why not have a table for each Module

    ie Contact module would have a Contact Table that the Field problem Sorted
    hope this help

    See clear as mud


    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB based on my own environment: vb6 sp5
    ASP based on my own environment: 5.6
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008
    MYLE
    YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.

  3. #3
    Join Date
    Dec 2007
    Location
    Richmond, VA
    Posts
    1,328
    Provided Answers: 5
    Sorry Stephan, but I would definitely stay away from that idea, as I could have thousands of modules, I do not want thousands of little module tables in my DB.

    Mbaughan,
    I would go with a code table of sorts. Something along the lines of:
    module name
    seq_no -- to allow for multiple items in a module
    typ_col -- to let you know what type of item it is sentto,etc...
    value
    maybe an on/off flag as well
    Dave

  4. #4
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,424
    Provided Answers: 8
    ok It was just and idea
    hope this help

    See clear as mud


    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB based on my own environment: vb6 sp5
    ASP based on my own environment: 5.6
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008
    MYLE
    YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.

Posting Permissions

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