Results 1 to 3 of 3

Thread: Database Design

  1. #1
    Join Date
    Aug 2003

    Unanswered: Database Design

    I am trying to get my company to switch from using Excel to using Access....

    I am a call manager and we have multiple sites.

    I needed some suggestions on the best design method...

    Should each site have their own databases?

    Should there be 1 centralized database?

    We allocate calls from site to site, so some of the queues in one site need to be rolled up into the stats of another....

    I was thinking of the following tables:

    800#'s, VDN's, Queues, Queue Statistics, CSP's, Nodes, Allocation's, CSP Stats

  2. #2
    Join Date
    Dec 2001
    First, either get an Access professional to help, or go through an Access tutorial yourself like the one here:

    >>800#'s, VDN's, Queues, Queue Statistics, CSP's, Nodes, Allocation's, CSP Stats<<

    These are not good table names.

    Don't use the "#" character in a table name, field name, or control name. It is "legal" but it will cause problems for you later on.

    Don't use single quotes in your table names.

    It's a good idea to NOT use spaces in your table names.

    It's a good idea to start all tables with a prefix like "tbl". Ex.: tbl800Numbers, tblVDNs, tblQueues, etc...

    Hope this helps to get you started,
    Peter De Baets
    Peter's Software - Microsoft Access Tools for Developers

  3. #3
    Join Date
    Aug 2003
    Delft, The Netherlands (EU)

    Cool Ask a professional

    .... or ask a professional like Peter to make a design! If you can affort it, it will prevent you from a lot of pitfalls; takes just a fraction of time; and lets you focus on your primair tasks.
    Make everything as simple as possible, but not simpler! - A. Einstein
    DB Problems? DB Explorer, BTrieve Re-engineering, DB Conversions & ETL? Conversion Tool

Posting Permissions

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