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

Prompt user for input in Report

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

    Prompt user for input in Report

    I am trying to do the following: when I click on a "preview report" button, have A5 show a dialog box for me to enter a short comment, and have the comment appear in the report. I can get A5 to show a dialog box (in the onPrintInit) to enter my comment but don't know how to place on the layout what was entered in dialog box. I then reversed the process, created a variable, placed it on the the layout, now I can't I enter my comment in it. I can't seem to connect both ends.

    #2
    Re: Prompt user for input in Report

    Gaby,
    Unless mistaken, the OnPrintInit event occurs too late for what you want to occur---and it and the OnRecord events are the only events you have in a report (wish there were more!).

    IOW any preprocessing has to be done prior to previewing the report...such as setting filters, order, variables, etc. .
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


      #3
      Re: Prompt user for input in Report

      Gaby, I agree with Mike. Collect your input. Store it in a global variable that corresponds to a global in your report layout.

      Comment


        #4
        Re: Prompt user for input in Report

        Mike,
        Not sure I understand this:
        any preprocessing has to be done prior to previewing the report...such as setting filters, order, variables, etc.
        I have a report where, thru xbasic, I create SHARED variables, open a couple of tables, get values from those tables and assign to my variables and use those variables in the report. All done in the Report OnInit event. Maybe with getting values from a ui_msg_box has to be done prior.
        Ernie

        Comment


          #5
          Re: Prompt user for input in Report

          [ATTACH]19813[/ATTACH]

          Comment


            #6
            Re: Prompt user for input in Report

            Originally posted by Tom Cone Jr View Post
            Gaby, I agree with Mike. Collect your input. Store it in a global variable that corresponds to a global in your report layout.
            Global Variable is the answer...I tried many things except globale variables; still learning...

            G Gabriel: your video shows exactly what I am looking for

            Thanks guys

            Comment


              #7
              Re: Prompt user for input in Report

              Ernie,
              I may have used the word preprocessing incorrectly---a bit too literal or all-encompassing I guess. Maybe looking at it in that any processing of values have to be done via code and not during user interface. There is another limit too in that like the system current_filter variable cannot be used (obtained or trapped) in the OnPrintInit event.

              Thanks for catching this.
              Mike
              __________________________________________
              It is only when we forget all our learning that we begin to know.
              It's not what you look at that matters, it's what you see.
              Henry David Thoreau
              __________________________________________



              Comment


                #8
                Re: Prompt user for input in Report

                Originally posted by gaby_h View Post
                G Gabriel: your video shows exactly what I am looking for
                Thanks guys
                It is doable. Someone asked the same question before and I attached an example. Unfortunately, it's Monday morning (or Tuesday) and I have absolutely no time to play with this. If you can't find the other example, I will try to attach another one later.

                Comment

                Working...
                X