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

Form level skip rule

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

    Form level skip rule

    Hi everyone,

    I'm building a questionaire. Some questions have to be skipped conditionally. Question 21 asks whether the respondent does any employee training. Question 22 asks for details. Obviously, if the guy does no training you skip question 22 and go on to question 23.

    Question 21 is a logical field displayed using a pull-down with the choices Yes and No and the values of t and f. The pull down is defined at the form level.

    I want to activate the question 23 field conditionally based on the the value in the control while the record is still unsaved. I have no trouble doing this with a type-in. It is the pull down control that is blocking me. I guess it is some type of object addressing problem.

    Does anyone have a suggestion.

    (I know I can write a skip rule in field rules but I am trying to avoid going this route.)

    Thanks very much,
    Bill
    Bill Hanigsberg

    #2
    RE: Form level skip rule

    Bill, assuming the tab order follows the question numbers, you could put something like this in the OnDepart event for the logical field at Question 22:

    vLogicalVariable = Question22.value 'where Question22 is 'object name of the logical 'field on the form

    if .not. vLogicalVariable then
    parentform:Question24.activate() 'where Question24 is 'object name of field on form
    end if

    Comment


      #3
      RE: Form level skip rule

      Hi Tom,

      That is an interesting idea, using an intervening variable. I was referencing the value of the control itself in the conditional expression.

      Here is the code I attached to Question21's on_depart:

      If this.value=.f.
      parentform.Q23.activate()
      End if

      Meanwhile, I fell across another clue. We had two versions of A5 running here and my syntax worked fine on the later version. But the machines have different versions of windows so I am in a bit of an inferential quagmire.

      I remember a passage in the manual which I think uses a variable as you suggest to refer to an object property. I just looked but failed to find it. I'll search further.

      Thanks,
      Bill
      Bill Hanigsberg

      Comment


        #4
        RE: Form level skip rule

        Place a conditional object on the form and make the object containing question 23 one of the conditions. Make the default a blank object.

        Comment

        Working...
        X