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

How to capture a query input.

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

    How to capture a query input.

    I am new to Alpha and am using v11. I have a report that when selected prompts the user for a start date and a stop date query for the report to be generated within. I would like to print the start and stop dates on the report. What is the best way to capture that info to place on the report?

    #2
    Re: How to capture a query input.

    a report that when selected prompts the user for a start date and a stop date
    If you are using ask variables for that purpose you will probably want to change to a form or xdialog requesting (your defined) global variables. You then use those global variables in the report's filter and you can place them on the report.
    There can be only one.

    Comment


      #3
      Re: How to capture a query input.

      On a event (button click) I am using the (prompt for parameters at runtime) option of the script genie currently.

      Comment


        #4
        Re: How to capture a query input.

        Same answer. You need a way to define the variables as global which you can then reference in the report.

        Take a look at the InvoiceReportMenu form in AlphaSports. Examine the code behind the Print/Preview button. This is essentiially what you need with the exception of the variables being defined as global for use in the report.
        Last edited by Stan Mathews; 06-29-2012, 11:42 AM.
        There can be only one.

        Comment


          #5
          Re: How to capture a query input.

          Thanks for the direction.

          Comment


            #6
            Re: How to capture a query input.

            Jerry,

            I am using prompt for date to and from on my reports and print them on the report using a5_GetArgumentValue()
            Just put a textbox on your report and set it up like this:
            Report Date.jpg

            ToDate and FromDate are my argument names.

            Stephen
            Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment


              #7
              Re: How to capture a query input.

              Thank you Stephen
              a5_getargumentvalue() is an undocumented function as far as I can see.
              What variable names space do your argument names get declared in?

              Comment


                #8
                Re: How to capture a query input.

                Originally posted by Ray in Capetown View Post
                a5_getargumentvalue() is an undocumented function as far as I can see.
                http://wiki.alphasoftware.com/A5_Get...Value+Function
                Visit to Specksavers Due?
                See our Hybrid Option here;
                https://hybridapps.example-software.com/


                Apologies to anyone I haven't managed to upset yet.
                You are held in a queue and I will get to you soon.

                Comment


                  #9
                  Re: How to capture a query input.

                  BACK IN A WHILE

                  I'm off to specsavers Ted.

                  (well actually I looked in the local help, then in Wiki just typed A5_getargument on its own, sinking zat it would match that part of the word)

                  Comment


                    #10
                    Re: How to capture a query input.

                    The good thing is Ray, that the comprehensive explanation (not) in the Wiki will enrich your enjoyment of the product for years to come. Children will gaze at you and point!
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/


                    Apologies to anyone I haven't managed to upset yet.
                    You are held in a queue and I will get to you soon.

                    Comment


                      #11
                      Re: How to capture a query input.

                      Pardon me for jumping in, but might this function help?

                      Comment


                        #12
                        Re: How to capture a query input.

                        The strange thing with that Tom - it most often displays just ".T." on a form or report
                        and when it does display the filter string, its not easily decipherable to the user.

                        Comment


                          #13
                          Re: How to capture a query input.

                          Originally posted by Ray in Capetown View Post
                          Thank you Stephen
                          a5_getargumentvalue() is an undocumented function as far as I can see.
                          What variable names space do your argument names get declared in?
                          Ray,

                          Have a look at this thread, see if it helps ... http://msgboard.alphasoftware.com/al...562#post567562

                          Stephen
                          Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

                          Comment


                            #14
                            Re: How to capture a query input.

                            Thanks Stephen, I will give it a go.

                            Comment


                              #15
                              Re: How to capture a query input.

                              Thanks Stephen
                              That appears to be in the report namespace.
                              From elsewhere it would need to be done either with Global vars (I avoid), or namespace - SESSION_VARIABLES( Session_Number ) pointer, that works but fills pages of drag/drop variables.

                              Comment

                              Working...
                              X