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

Calling a report with variables

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

  • Calling a report with variables

    I have a membership database. I regularly need to pull reports, which list all the members of the various clubs. However the summaries (all calculated fields - recording numbers of deaths, resignations, exclusions, joining members for each club), need to reflect the period in question.

    I tried using two date fields date1 [set as 01.07.2000]and date2 [date1+364 = 30.06.2001] which worked fine.

    I then added a script in the calling routine, which set date1 as a variable fallowing a ui_get_date call. The programme crashed badly, so that I cannot edit, view or print that report at all.

    What is the easiest way to call a report with variables, bearing in mind that the database dhould not be filtered, ranged, sorted or any other thing?

  • #2
    RE: Calling a report with variables

    There are several discussions of using variables (from a calling script) to filter reports, just search the board.

    On another note you state:

    "which set date1 as a variable fallowing a ui_get_date call"

    - I assume you are aware that ui_get_date() returns a character string which must be converted to a date? usually performed with ctod()

    I sometimes forget that all the ui_get.. functions return character strings and the returned value must be manipulated.
    There can be only one.

    Comment


    • #3
      RE: Calling a report with variables

      Wasn't as easy to search for as I first thought - here's and example.

      Msg ID: 41702
      Subject: RE: Report Variables
      Author: Bill Warner
      Date: 05-23-2001 10:22
      File:

      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.
      There can be only one.

      Comment


      • #4
        RE: Calling a report with variables

        OK I didn't set out all that I had done.

        I had converted the dates to actual dates rather than characters by using ctod.

        In the report I had calculated fields on the lines of "Report starting from "+alltrim(str(date1)) etc. I also had calculated fields counting the numbers of members falling within the two dates etc.

        However it would appear from reading the other forum entries that if the field thinks that the date is blank, it falls over, and that is what happened to me. I now cannot print, review or edit the report.

        How do I ensure this cannot happen.

        In the Xbasic book, there is a suggestion about using the input into the onprintinit, but that option does not seem to appear on my reports.

        Comment


        • #5
          RE: Calling a report with variables

          Colin,

          Perhaps your variable date1 needs to be global.

          To insure that it's not blank when the report is called, add a line to the button script which calls the report, and assign a default value to the variable before the report is opened.

          If you have blank dates in your data tables, they can be filled with default values using an update operation. Once they're all filled, you could modify your data entry routines to prevent a new record from being saved whenever the date field is blank. Should help a lot.

          -- tom

          Comment


          • #6
            RE: Calling a report with variables

            Try looking for my "Set Dates" example in the code archive this should help.
            Terry

            Comment


            • #7
              RE: Calling a report with variables

              Colin,

              Here's a simple example illustrating one approach to calling a report, and filtering it's output based on variables supplied by the user.

              Unzip the attachment to a separate folder. Do not mix it with your development work.

              -- tom

              Comment


              • #8
                RE: Calling a report with variables

                Colin,

                I've expanded the example to include illustrations for:

                1) using variables to filter detail records in the called report.

                and

                2) leaving the detailed records unfiltered, but using variables to count number of records that fall within the specified date range.


                On re-reading your original post I think possibly the second case will be closer to what you are looking for.

                -- tom

                Comment

                Working...
                X