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

Set Design Problem

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

  • Set Design Problem

    Trying to create a many to many set as follows:

    Names
    ==Weekdays
    ----Time

    Weekdays = sun,mon,tue, etc. for a total of seven static records in the table.

    The Time table has a "week_ending_date" field as well as a date field for the particular day of the week. The week_ending_date feld allows a query of records for any given week.

    Time has one record per Name per date, but not usually for all days of the week.

    The trouble is that weekdays is generic, whereas names & Time share a common ID field.

    The bottom line is that I need to print a weekly report that list all 7 days of the week for each name, and lists the corresponding time data for each day of the week.

    In other words the report output should look like this:

    John
    ==Sun--8 hours
    ==Mon--8 hours
    ==Tue--8 hours
    ==Wed--7 hours
    ==Thu--8 hours
    ==Fri--8 hours
    ==Sat-- (i.e. no Time record)
    ==Sun-- (i.e. no Time record)

    Sue
    ==Sun--6 hours
    ==Mon--8 hours
    ==Tue--8 hours
    ==Wed-- (i.e. no Time record)
    ==Thu--8 hours
    ==Fri--8 hours
    ==Sat-- (i.e. no Time record)
    ==Sun-- (i.e. no Time record)

    ETC, ETC.

    Does that make any sense? Is that doable somehow?
    Peter
    AlphaBase Solutions, LLC

    Peter@AlphaBaseSolutions.com
    https://www.alphabasesolutions.com



  • #2
    RE: Set Design Problem

    Oops. I showed a duplicate Sun record above.

    John
    ==Mon--8 hours
    ==Tue--8 hours
    ==Wed--7 hours
    ==Thu--8 hours
    ==Fri--8 hours
    ==Sat-- (i.e. no Time record)
    ==Sun-- (i.e. no Time record)

    Sue
    ==Mon--8 hours
    ==Tue--8 hours
    ==Wed-- (i.e. no Time record)
    ==Thu--8 hours
    ==Fri--8 hours
    ==Sat-- (i.e. no Time record)
    ==Sun-- (i.e. no Time record)

    ETC, ETC.
    Peter
    AlphaBase Solutions, LLC

    Peter@AlphaBaseSolutions.com
    https://www.alphabasesolutions.com


    Comment


    • #3
      RE: Set Design Problem

      Peter,

      There's probably a more elegant solution, but the first thing that comes tomind here is that the intermediate table is full of nothing but constants (days of the week). I would examine whether such a structure is needed.

      For example, couldn't you do a two table set, with Names as parent table and Workdays as child, linked one to many on the employee idnumber. The Workdays table would contain both the date worked and the hours worked. The date worked could be used to break out the records on a week by week basis couldn't it?

      If you need to list all seven days of the week, even if no hours are worked on some days, this sounds like more of a report design problem, than a data entry design issue. Perhaps you could export the records for a week to an intermediate table. Then run a script to stuff zero hours worked entries in records for the missing workdays... then base your report on the intermediate table.

      Like I said, others may have more elegant solutions, but perhaps this will give you some ideas.

      -- tom

      Comment


      • #4
        RE: Set Design Problem

        >>Perhaps you could export the records for a week to an intermediate table. Then run a script to stuff zero hours worked entries in records for the missing workdays... then base your report on the intermediate table.
        Peter
        AlphaBase Solutions, LLC

        Peter@AlphaBaseSolutions.com
        https://www.alphabasesolutions.com


        Comment


        • #5
          RE: Set Design Problem

          Just thought of an easier way. Scrap the set design issue. I will pust labels on the report for the 7 days and use report calc fields to evaluate the DOW(date)=tbl.date(), and then print the corresponding field values. If there is no corresponding record to the day of week, I will still get printed values for my form, which is what I want.

          Whew!
          Peter
          AlphaBase Solutions, LLC

          Peter@AlphaBaseSolutions.com
          https://www.alphabasesolutions.com


          Comment


          • #6
            RE: Set Design Problem

            Peter,

            You may find that determining

            ' If there is no corresponding record to the day of week '

            is hard to do. It's like finding something that isn't there. Let us know how it turns out.

            -- tom

            Comment


            • #7
              RE: Set Design Problem

              Tom,

              Actually, "my" method works, because it doesn't depend on the existance of actual records. I merely place labels as needed in a group footer, and I create corresponding summary calc fields to display the appropriate field values for when there are records. This method requires two calc fields. The first just captures the field value when the DOW evaluates to the corresponding day of week date, the second calc filed is a summary of the first calc field - usually using the "maximum" function. This last field is what is actually displayed in the group footer. This method is calc field intensive. In my case, for 7 days of the week, a total of 14 calc fields are required for each field you wish to display. But the report generator calcs those values instantaneously. Works very well.

              Peter
              Peter
              AlphaBase Solutions, LLC

              Peter@AlphaBaseSolutions.com
              https://www.alphabasesolutions.com


              Comment


              • #8
                RE: Set Design Problem

                Ahh! I see it now. Thanks. -- tom

                Comment

                Working...
                X