Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Attendance System

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Attendance System

    I need help with an attendance system which has been bothering me for a while.
    The Scenario: A company provides Seminars (expl a seminar on Gardening in April, a seminar on Programming in June, etc...). Each seminar is divided into sessions/days (session1, session2, session3, etc...). People sign up for a seminar of their choice. Say, 25 people signed up for Seminar7 that has 5 sessions. The 25 names are recorded in a Registration table which is a child table of Seminars. Thus, when viewing a parent record (Seminar) we can can see the list of people who signed up for each Seminar. So far so good.
    My big issue is designing an attendance system to keep track of who showed up, who did not. The best I could do was this:
    I created an Attendance table with the following fields: SeminarID, SessionID, Name, Attended (T or F).
    For each session, I import the names from Registration table for the parent record and select T or F if the student attended or not. For expl: If 30 people signed up for Seminar28 (Registration tbl for this Seminar shows 30 child record) that has 5 sessions, the Attendance table receives 5 times the 30 same records=150 records to keep track of attendances; in other words, a name is duplicated as many times as there are sessions in a seminar. This is clearly not an efficient way. An Excel version would have the 30 names listed only once in rows and 5 columns (1 for each session) where the user just tick T or F.
    Any suggestions, pointers will be highly appreciated. Thanks

    #2
    Re: Attendance System

    I struggled with this as well. To be efficient, I de-normalized a bit. I created an Attendance table with SeminarID, StudentID and then 60 Session columns S_01, S_02, etc field type T/F. Sixty was selected as the maximum number of sessions any Seminar would ever have. The SeminarID ties back to a Seminar table with 60 SessionDate columns. So in my Attendance table I have only one record for each Student per Seminar. Pain comes when you need to run a report of who attended between dates, etc. But it is also easy to add a Student late in the seminar series.

    Also, on the data-entry side they don't bother to record who is present, they only record absence. So, in the table a True=Absent.

    I don't know if my method is best practice so I hope others will also discuss.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Attendance System

      Hi Steve:
      I had thought and tried that route a few months ago but hit 2 issues:
      1)the Attendance grid will always show all the 60 columns; so need to dynamically hide the unnecessary columns depending on the nbr of sessions of each seminar.
      2) Need to dynamically display in Attendance grid the session dates ascending from left to right as col heading instead of Session1, Session2, Session3.... or Day1, Day2, Day3...
      Will give it another shot.
      Thanks for replying.
      Attached Files

      Comment


        #4
        Re: Attendance System

        This is always a problem. You could do it the normalized way, where there is one set of session records (grandchild) for each student w. a (T/F) attendance. Then use a report w. calc fields to display the results horizontally. But otherwise, I like Steve's method.
        Peter
        AlphaBase Solutions, LLC

        [email protected]
        https://www.alphabasesolutions.com


        Comment

        Working...
        X