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

Passing Parameters

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

    Passing Parameters

    How do I put the value of a calculated field from a report into a global variable so that I can use it in a report from another table?

    #2
    RE: Passing Parameters

    Ronald, good question.

    If you arrange to assign the calculated field value to a global variable, the second report should be able to see it at print time, provided it is declared global there, as well.

    Assigning the calc field value to the global variable initially can be done by hooking a short xbasic script to a Section Event in the first report layout.

    For example I just did this to test the concept:

    1) dropped a numeric global variable on a form;
    2) declared it in a report layout based on the same table as the form;
    3) defined a calc field in the report to display the running count of records in the report and dropped it in the report footer;
    4) in the Section Event GRAND I attached the following script:

    var->CurrCount = Calc->Rpt_count

    to assign the calc field value to the variable.

    After running the report when I go back to the orignal form, the value of the global variable matches the computed value in the report.

    -- tom

    Comment


      #3
      RE: Passing Parameters

      Thanks Tom for the much needed guide to transferring this information. I know very little about variables and events, so I tried to educate myself about them, and was able to define the global variable and drop it on the form as in your first step. I don't know if I succeeded to declare it in the report based on the same table - I redefined it just as I had in the form. Then, since I already had a calculated field created, I tried to attach a script to the section event Grand, but when I checked the variable in the design mode of the form, it hadn't changed. I think that I need more specific instructions on how to do the attachment - and is there another way to check the value of the variable?

      --Ron C.

      Comment


        #4
        RE: Passing Parameters

        Ronald,

        Try this.

        Open the report layout in design mode.
        Open the form menu.
        Click Variables.

        Do you see your global defined there? If not, add it being sure to use the exact spelling as you used when you dropped the global variable on your form.

        Run the report.

        Open (view) the form. (Don't open in design mode).

        -- tom

        Comment


          #5
          RE: Passing Parameters

          Thanks Tom - I now have the variable working properly. I had thougth that the place to look for the value of the variable was in the box where it was created because there was a "value" column there, which it now appears is used to set an initial value of the variable. Thanks for your help.

          Comment

          Working...
          X