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

Radio Button

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

    Radio Button

    I have created a very simple database to store a listing of titles of movies that are on DVD and VHS. I created 2 Radio Dialogs and followed the step by step procedure from the PACE Alpha 5.5 level 2 pages 183-205. The Buttons are as follows. Sort by: DVD; and Sort by:VHS. The other Radio Dialog buttons are: Preview" ALL Media Titles; DVD Media Titles; VHS Media Titles. The problem is if I press the action button and it opens up one of the Radio Button Dialog, when I select "Cancel" it runs the operation any way. If I open the Radio Button Dialog for previewing a report, and select "Cancel" with or without selecting one of the options, it runs the preview report anyway.

    I have played around with this for about three days to try to figure it out, even doing the Radio Button Dialogs from scratch several times and come up with the same results.

    As a side note. I don't understand XBasic and do everything in Action Script. I search this message board to see if there is anyone with the same problem but didn't see any.

    Thank you in advance
    Allen Breen

    #2
    RE: Radio Button

    From the please read before posting...

    The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. "b"A sample table with a minimum of
    records (and its support files, zipped together) will make it much easier to diagnose issues"/b" with lookups, Xdialogs, etc. Screen shots of error messages are especially helpful.


    It would be so much easier to see what might be wrong with your buttons if we could just see how they are designed to operate.
    There can be only one.

    Comment


      #3
      RE: Radio Button

      Allen,

      Stan is correct. We would really need to see the code generated behind the buttons in order to accurately assist you. You mention using action scripting. I would take a guess that what has happened is that there is no 'action' programmed for when the user selects the cancel button.

      You would need to convert the action script to xbasic and then add additional code to tell it what you want to do when the user clicks the cancel button, like close the dialog and do nothing.

      Good luck
      Cheryl
      Cheryl
      #1 Designs By Pagecrazy
      http://pagecrazy.com/

      Comment


        #4
        RE: Radio Button

        Allen,

        You need to make a conditional action that fires on the "UI_CANCEL". This action should be to "stop execution".

        Tom

        Comment


          #5
          RE: Radio Button

          Here is the Home Inventory.ZIP file. the only thing I have really been working on is the Media Inventory DBF.
          I don't do these databases except for my home use only, so I am not at all well versed in these things. I only pick up bits and pieces from wherever I can for the project that I happen to be working on for myself. So any corrections and responeses that are explained to me will have to be in real easy to understand terms. That is why I prefer the Action Scripts because I can compare them. Xdialog is Greek to me.
          :)
          Thanks again for your help and imput.
          Allen

          Comment


            #6
            RE: Radio Button

            I have had the same issues. I created an append feature in operations with date willing with an "ask variable" for the date field.

            If they select Cancel when the variable box opens, it appends anyway, it just leaves the date field blank. I have a lot of these features where it asks for some type of filter ask variable, and I am finding that Cancel rarely works.

            Here is what I have: Operation - Update
            Filter: STATUS="Closed".and.POSTMARK=.t.

            INVOICEDATE Var-"askD_Date_to_Post_To
            STATUS "Invoiced"

            The button that runs this, is

            'Run an Operation that was previously defined.
            query.filter = ""
            query.order = ""
            DIM operation_name as c
            operation_name = "Sls - POST Sales SLC"
            If operation_name "" "" then
            update.run_silent(operation_name,query.filter,query.order)


            Do I put a command in the button script that says if the var-ask date is empty, or cancel is pushed, stop. Or is there a way to specify this in the Operation?

            Comment


              #7
              RE: Radio Button

              Lynda,

              I think maybe it's time for you to graduate to regular variables in order to gain the control you need. Yes, your script should prompt for the variable, and if the string returned by the user is empty you need to END the script. As others have noted for you elsewhere the CANCEL button on the ask_var dialog simply cancels input from the user. This works correctly. It was never intended to terminate the running script. -- tom

              Comment

              Working...
              X