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

subtract or scaning

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

  • subtract or scaning

    Morning

    I have a table with names, info, etc., linked to many other tables, one being a table of one to many of late & absents ( date, reason, ID #). I have reports of students and their dates of being late and / or absent.

    I would like to make a report of students who were not absent throughout the year.

    It looks as though I can use the subtract operation and make a table of those ID's who didn't have an absent day and then link this result table back to the primary to report on those who weren't absent.

    Or the Scanning function may do it right in the report detail filter!

    Can someone shed some light on this?

    Thanks

    Duane

  • #2
    RE: subtract or scaning

    I believe scanning returns a logical value.

    I use it to check for child records in onrowdoubleclick in embedded browses to deny the code if there are no child records

    you can say
    parent=customers
    child=hearing aids
    form(or report) is open on that set

    if scanning("hearing aids") 'found some children
    'code for event
    else
    end
    end if

    or I can say
    if .not. scanning("hearing aids") ' didn't find any
    end
    end if
    'code for event
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    Comment


    • #3
      RE: subtract or scaning

      Duane,

      Hey, it's 2:30 am and I'm wide awake. UGH!!! But...........I assume the table with the names is the parent table and the table containing the *absents* is a child table, linked 1:m to the names table.

      Assuming you record a T or Y in the absent field in the child table if a child is absent, using a report, couldn't you set up an expression in the Report Detail that will show all names (parent table) where the absent field is:
      is blank or the field is empty.

      That's what I would try for a start.

      kenn
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment


      • #4
        RE: subtract or scaning

        Duane,

        Hey, it's 3:30 am. what am I doing out of bed?

        It's not clear how you can distinguish a record of an absence from a record of a late arrival. Assuming you have a way to do that, then here's a brute force approach you might try.

        1) unmark all the name records

        2) invert the set, make the child table the parent, and the former parent becomes the child, linked one to one

        3) run a query against the new parent table to find only the absentee records

        4) mark each corresponding name record... i.e. mark only the name records in the current query list of absentee records

        5) close the set, and open the original set, run your report but filter it so that only unmarked names are included.

        6) to be tidy, remember to unmark all name records when finished.

        This approach assumes that you only have records for the current student year in your tables...

        The problem you're facing is how to identify things that 'aren't there'. You've recorded absences... and now you want to list the ones that have no absences... What I'm recommending is that you 'mark' the ones that had absences... and then run your report filtered for those who are 'not' marked.

        If you put your lates in one table and your arrivals in a second table I think things would be easier. You could then use the exist() function to determine which name records don't have linked absentee records... You can't do that now because someone might have been late a few times, but never absent. Their name record would have one or more linked child records (because of the lates) but they were never absent.

        Now back to bed.

        -- tom

        Comment


        • #5
          RE: subtract or scaning

          Couldn't you just put together another set of just student records to "absent" child records. (there MUST be a way of identifying them) The it is just a matter of using the .not.scanning to see those that have no absenses.

          Comment


          • #6
            RE: subtract or scaning

            by the way,
            you guys definitely stay up way too late at night.

            Comment


            • #7
              RE: subtract or scaning

              Afternoon (already)

              Thanks for the replies
              Making a new traditional set for the report and using the .not.scanning("absentees") worked just fine.
              Using the original set, the scanning function was also picking up records from other one to many links in the set.
              Making up the new set works just fine for finding the non absent/late students. Using a filter in the new set link properties to only use the absent/late field = "absent" kicks out the late kids from the reporting system.

              I think all is well (for now).

              Thanks
              Duane

              Comment

              Working...
              X