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

Run Time Input

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

    Run Time Input

    I like to be able to have a user enter query information when a query (browse) is run. I am use to using the Access paraneter query with the [ ] feature. With this Access feature you can prompt the user and accept input. Does Alpha have a similar command and/or how would accomplish a task like this?

    Thanks for your help!

    #2
    RE: Run Time Input

    As one example, you could create a button to which you would attach a script. This script could prompt for info (using ui_get_text, for example) which would generate values for variables. These variables could then be used in the script that would run a query.

    This is quite a common procedure in many applications. For example, to run a report showing sales for a given date range, you would prompt the user for start and end dates, plus perhaps the company ID. The resulting variable would then be used in a query, or in the filter for the report.

    You're really only limited by your imagination!

    Comment


      #3
      RE: Run Time Input

      Hi Ron,

      I have/am been/going down your road. Trying to grasp the various ways in A5 to do this can be confusing but they are relatively easy. And, it depends on how you want to use it. If it's to generate a report, then Bill's suggestion works as well as this suggestion. (These can be placed on the button which opens the report or on the repoort's Detail Properties)

      When you create a Query By Table, you can use the Ask_Var. Say you want to prompt for a range of dates. After draging the date field, go to the Var column (it's to the right of the tables) and drag the to the condition column. Enter the text you want the user to see, such as "Enter Begin Date" (" not needed). Drag the date field to the 2nd line and do the same with the , this time enter, "Enter End Date". Make sure you select "Date" for the Type. This will do what you want and is the easiest and quickiest to set up (for new learners). It can't be customized as Bill's suggestion but it's quick and easy.

      Note: If you run a specific query a lot even though it's not a report, these methods can be placed on a button.

      A 3rd way is very useful for creating queries to view data but not via a report. Use Query By Form and in the date field enter the search dates as follows: 1/1/01..9/1/01 Click the lighting bolt and walla. This will give you all records which fall between that range of dates. A5's QBF is much more flexible that Access QBF.

      TIP: When doing something in A5, FORGET how it's done in Access. Alough there are similar procedures, I found that focusing on A5 and not trying to do it the way Access does, causes a lot less confusion.

      Hope this gets you started.

      kenn
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment


        #4
        RE: Run Time Input

        Here's a pictiure of a form opened as a dialog, that lets the user select several possibilities. When the form loads, I definbe a group of global variables. When the user selects continue, I use the variables to find clients that meet the desired query from several tables - then I delete the variables. Hope this gives you some ideas.
        Cole Custom Programming - Terrell, Texas
        972 524 8714
        [email protected]

        ____________________
        "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

        Comment


          #5
          RE: Run Time Input

          Ron,

          Just as Kenn suggested as an option, I use a query by form with a special form to create query filter and order expressions. I then use the developed expressions to run a report with the filter and order expression. (Tom Cone posted a sample form that shows how to trap the filter and order expressions on 9-4-2001). Also check out ui_get_expr() as a simple way to get a simple expression.

          Jerry

          Comment

          Working...
          X