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

Report Variables

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

    Report Variables

    I have a series of 4 reports that are run one after the other. They all cover the same variable report period. I have set up report layout variables for each report. As the reports run, I have to enter the report start and end periods (all the same) for each report.

    I'd like to be able to enter the start and end periods just once and have all four reports print for the same period.

    #2
    RE: Report Variables

    Ed:
    What I usually do for report date ranges (current and job to date)
    I usually take the master database and summarize records to what I need on the report.
    Then I append into a print database that has about the same structure as the report database,except that it has additional fields.(datebeg,dateend,curhours curdollard,jtdhours,jtddollars..and any others that I need)
    I prompt the user 1 time for the dates by using scripts.
    I post that info to the print table in the fields datebeg and dateend.
    I then do an update to update the fields in the table based on the beg and end dates.
    then print reports.
    The user can go back and change the dates for the reports and run the updates without having to re-summarize all the tables.
    Charlie Crimmel

    Comment


      #3
      RE: Report Variables

      Create a form, create form level variables named the same as your report variables- make them global, put fields on the form for the entry of the variables, put a button on the form to run the reports.

      The reports will have the needed variable information available at print time.
      There can be only one.

      Comment


        #4
        RE: Report Variables

        Here's a script I use to establish start and end dates. You'll note that I have declared the variables as global, so I can use the dates whereever I want:

        dim global d1 as d
        dim global cd1 as c
        dim global d2 as d
        dim global cd2 as c

        cd1=ui_get_date("START DATE","Enter start date.",dtoc(d1))
        cd2=ui_get_date("END DATE","Enter end date.",dtoc(d2))

        d1=ctod(cd1)
        d2=ctod(cd2)

        D1 and D2 are the actual date variables (CD1 and CD2 are the character equivalents, and are only used in this script).

        You would use VAR->D1 and VAR->D2 to evaluate your start and end dates in each report.

        Comment


          #5
          RE: Report Variables

          Many Thanks. Bill, worked like a charm. Have had a mental block trying to use Global variables, but your example cleared it up completely. Thanx again.

          Ed

          Comment


            #6
            RE: Report Variables

            Just an opinion, but I think you really should consider Stan's approach via a form, preferably a dialog form. It is all too easy to make a mistake in typing dates and not catching it until you have 4 printouts sitting in your printer. On a form the user has a chance to visually verify that the dates are proper, even indicating what days of the week the dates fall on. Morover, you can have A5 do some validation, such as that the end date is after than the start date, or is not in the future, or is at least a month ago, etc. Peter Wayne's Xbasic for Everyone has a section on this subject. The form could also give you other ways to easily filter the report, say a date range but also only for a particular sales rep (or all of them if that variable is blank or perhaps All).

            Just a thought.

            Raymond Lyons

            Comment


              #7
              RE: Report Variables

              Guys:

              I'm a jerked over A4 guy and here's what I do.

              A dialog form 'Whatdate' [opened non-dialog] holding global date variable start and end fields. At menu start up I set these to 01/01/[current year]for begin and DATE()[system] for end. I also declare a global variable "Report" a menu init.

              The "O.K" button's action on this 'Whatdate' form names the Report Name and plays a script with the syntax created by Alpha for a print button, however, the report name in that syntax has been edited to 'Var-report' for both print and preview. The 'Cancel' button stops the whole activity with 'Form Close'

              When all of this plays, the user can accept the dates which are essentially 'year-to-date' or change them - the change will 'stick' for any subsequent report actions.

              I'm sure there's may other good ways but this works just fine for me.

              Ken the Newbie

              Comment


                #8
                RE: Report Variables

                Ray...many thanks for your thoughts. Stan's approach fits a couple of my apps. Bill's fits a few too. It's nice to be able to select the best approach based on the app.

                Ed

                Comment

                Working...
                X