Results 1 to 3 of 3
  1. #1
    Join Date
    Jul 2009

    Unanswered: Not sure how to do this...

    I have been tasked with creating a database to track employee OJT. My problem is admin wants detailed info and reporting and I am not sure how to do this.

    My attempt thus far has been to organize the training into topical areas and having the checklist for specific tasks placed in a table labelled as the topic. This process results in around 100 tables with 2-20 fields. The data for those fields is either Instructed, Performed, or Tested. I have info linked to each table for basic info like trainer, date, shift, etc. On average 10-15 topics are covered each training day, but there is no strict procedure as to which topics are covered when so it varies.

    Now, making the tables and such is easy. How on earth can I create queries to search topics covered by date (to see what was done on a given day), or trainer (to see what all a given trainer taught), or tested (to see when each topic was tested and by whom). To simplify things, I am making each new hire a separate database.

    Any help would be great!

  2. #2
    Join Date
    Nov 2007
    Adelaide, South Australia
    Easily. IF the structure is correct. Perhaps designing tables is not as easy as you thought?

    Mods, please change the topic title to something meaningful.
    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

  3. #3
    Join Date
    May 2009
    To simplify things, I am making each new hire a separate database.
    This is very worrisome. You should not be creating a separate database for each new hire, that will be a maintenance nightmare. If you do it that way, forget the possibility of querying for the new hires that a specific trainer has trained.

    StarTrekker is right, if your database is well-formed, there should be no problem with what you are attempting. Separate databases for each new hire... not even a considerable option.


Posting Permissions

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