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



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

Report - Section OnRecord Event

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Re: Report - Section OnRecord Event

    Mike and Tom,
    Thanks for your help with this. As to my original question, the answer seems to be "No".

    Thanks for your input. As to my original question, as stated above, it can't be done. But there are workarounds, as you've shown. Thought I had tried the footer option, but maybe I didn't. My intent was to get the ending values from the last record in the parent table to print in the header or footer. Thought using a variable to do this might work. But looks like there is no way to do that. By placing the ending value fields in the footer, it comes up with the correct number, but may not be from the last record in the parent table. So I can just label it as Ending values.


    • #17
      Re: Report - Section OnRecord Event

      Originally posted by enstorms View Post
      as stated above, it can't be done.
      Yes there is a way to use the OnRecord events (not in this scenario) and yes there is a way to use a variable (not in this scenario either). This thread seems to mix Jazz with Rap with Beethoven.. I steered clear from discussing this issue until first you are clear on what the answer to your question is. Will get to that later if you are interested.

      Since I wasn't quite sure what you were trying to do, I attached an image of the results to see if they reflect the right numbers.

      Reading your last post, I now understand fully what you are trying to do. Interestingly enough, right after I started reading your original question, I knew right off what the answer should be before even finishing the question. Sometimes, I have the bad habit of responding without reading the whole thing. I was about to do so, but then when I read the whole thing I became unsure about your intentions.

      The correct answer is you need a calc value not a variable nor an OnRecord event.

      Your set has a filter that only shows records from the parent that have child records. Now you want to get a value for a child from a parent that may or may not be included in the report. This seems to be the part that got you off track.

      I can't quite remember now if the value I placed in the footer was from the parent or the child. I just used whatever lookup() you used to obtain the same value. I think you need to make a correction here:
      If you want to place the last value of the parent, you need to use a different function: you need lookupc() or lookupn() ... But, let's be clear what last means: last means the one that was added to the table last, i.e. the one with the highest recno. If however you are looking for the one with the highest value, then you need a completely different function: dbmax().

      You could place this calc value in the details section or the footer, it does not matter. Only difference is, in the details section, it will repeat with every record.
      Last edited by G Gabriel; 12-14-2008, 01:43 PM.


      • #18
        Re: Report - Section OnRecord Event

        Really appreciate your help. I did try to use the calc field before, but was using the lookup() function instead of lookupn(). So that makes the difference. Guess I didn't want to have to use an index for the lookup since it is made up of 3 fields. Still learning how to concatenate fields together, although numeric fields are pretty simple.
        Thanks again.