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

ui_get (s)

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

    ui_get (s)

    A search here didn't reveal the answer.
    Problem: Report doesn't stop for input of the week. Stops to get "TO" but then flies right on by to show report.
    Code extract follows:
    ----------
    Dim global sto as C
    Dim global nweek as N
    '
    '
    sto = ui_get_text("TO:","Send to ?",sto)
    'nweek = ui_get_number("WEEK:","Week of Report?",25,00)
    'nweek = ui_get_number("WEEK:","Week of Report?",nweek)
    ----------
    Neither nweek works. the week of course would be 1 through 52. The variable is specified as numeric. a flyover shows the field as 19.2. Maybe the first nweek would work - with the 00; however, the report never stops for the second input. Done with Design -> Report -> On Init.
    A5V5, latest build.
    Thanks
    Dick

    #2
    RE: ui_get (s)

    Dick

    The documentation is a little vague, but ui_get_number() prompts for a number but returns a character value. Therefore, both of your expressions for nweek will fail because nweek is numeric. Try changing to numeric

    nweek = val(ui_get_number("WEEK:","Week of Report?",nweek))

    Jerry

    Comment


      #3
      RE: ui_get (s)

      Thanks Jerry. Will give it a shot, sounds reasonable.
      Dick

      Comment


        #4
        RE: ui_get (s)

        Tried it and it still doesn't make the second stop. After inputting the "To:", it whizzes right on by and outputs a report without pausing for the week input.
        Dick

        Comment


          #5
          RE: ui_get (s)

          where is the code? is it in a report event?

          can you zip the files up and attach them so that we can duplicate the problem

          Comment


            #6
            RE: ui_get (s)

            Richard:

            In your code as posted

            sto = ui_get_text("TO:","Send to ?",sto)
            'nweek = ui_get_number("WEEK:","Week of Report?",25,00)
            'nweek = ui_get_number("WEEK:","Week of Report?",nweek)

            I see that each of the nweek lines has an apostrophe at the beginning. If they are also in the code as you run it they will prevent the line from executing.

            But perhaps I am only seeing a cut and paste issue.

            Bill
            Bill Hanigsberg

            Comment


              #7
              RE: ui_get (s)

              The apostrophes are not in the actual code. Was trying different "flavors" and just put 'em in as part of the test process.
              Dick

              Comment


                #8
                RE: ui_get (s)

                Yes, it is in a report event, Init on Print.
                Will extract the relevant tables from the db, zip, and send 'em to you. Thanks.
                Dick

                Comment


                  #9
                  RE: ui_get (s)

                  Dick

                  Since you are using global variables, it would be easier to call the report from a script and set the variables in the script first. This would eliminate even using the OnInit event.

                  Jerry

                  Comment


                    #10
                    RE: ui_get (s)

                    Thanks. I must be missing something. If I hard code the data, doesn't it preclude getting the input from the user?
                    As I understand the instructions, the variables have to be either shared or global. The latter was just arbitrarily chosen.
                    Dick

                    Comment


                      #11
                      RE: ui_get (s)

                      Dick

                      I just tried your code in the interactive window and see a problem I missed. Both of these will fail, since the default parameter and format are character inputs.

                      'nweek = ui_get_number("WEEK:","Week of Report?",25,00)
                      'nweek = ui_get_number("WEEK:","Week of Report?",nweek)

                      Both of these will work.

                      nweek = ui_get_number("WEEK:","Week of Report?","25","00")
                      nweek = ui_get_number("WEEK:","Week of Report?",alltrim(str(nweek)),"00")

                      The concept of using a script is to put this code in the script and then run the report using the format

                      Report.Print(Layout Name, [Filter expression], [Order expression])

                      in the same script. If you use this method, you have more flexibility with the report since the filter and order are defined outside the report. This allows the report to be used for multiples actions and different filters and orders since that is not set in the report inself. This is covered in the xbasic manual at about page 181 under print preview and gives a number of examples.

                      Jerry

                      Comment


                        #12
                        RE: ui_get (s)

                        Thank you Jerry. Will give it a go. Will review the reference too. Thanks again.
                        Dick

                        Comment


                          #13
                          RE: ui_get (s)

                          Thanks again Jerry. Works great. Guess I was close, but no cigar. Thanks again.
                          Dick

                          Comment

                          Working...
                          X