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

Skipping a field

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

    Skipping a field

    Hello, I'm new hear and I'm stuck on a problem.

    I have a field that I need on there if I'm going to use it, but if not, I want it to disappear off the form. I can't just skip it and leave it blank because it doesn't need to be on there at all if I don't need it. Any suggestions?

    Thanks
    britt.rose

    #2
    Originally posted by britt.rose
    Hello, I'm new hear and I'm stuck on a problem.

    I have a field that I need on there if I'm going to use it, but if not, I want it to disappear off the form. I can't just skip it and leave it blank because it doesn't need to be on there at all if I don't need it. Any suggestions?

    Thanks
    britt.rose
    Each object on a form has a "visible" property which can be set to true or false based on some criterion.
    There can be only one.

    Comment


      #3
      Originally posted by Stan Mathews
      Each object on a form has a "visible" property which can be set to true or false based on some criterion.
      Where would I go to set the visible properties?

      Comment


        #4
        Brittany, the basic idea would be to find an event that will occur when your end user is using the form that you can use to attach a script that will set the property of the object for you, depending upon whether the antecedent condition is present or not. How will Alpha Five "know" if the field should be skipped or processed? (i.e. describe for us the conditions that would be used by the form to know whether to display or hide the field object.)

        --tom

        Comment


          #5
          Originally posted by Tom Cone Jr
          Brittany, the basic idea would be to find an event that will occur when your end user is using the form that you can use to attach a script that will set the property of the object for you, depending upon whether the antecedent condition is present or not. How will Alpha Five "know" if the field should be skipped or processed? (i.e. describe for us the conditions that would be used by the form to know whether to display or hide the field object.)

          --tom
          Depending on what kind of Purchase Order number that is entered, that's how it should know. An example would be the Purchase order number would be "EPI222" and that's when it would need the specific field. But if the Purchase order was in the format "REG6546" the field wouldn't need to be on there.

          Comment


            #6
            Originally posted by britt.rose
            An example would be the Purchase order number would be "EPI222" and that's when it would need the specific field. But if the Purchase order was in the format "REG6546" the field wouldn't need to be on there.
            This probably has some significance to you but doesn't provide us with enough information to guide you.

            Do you mean to say that only purchase orders that have the "EPI" prefix will need the other field? Do you mean to say that any purchase order that doesn't have the "REG" prefix will need the other field?

            You can program any logical condition you wish into the display of the other field but you must be able to express that condition in logical terms.

            You could use the ondepart event of the purchase order field to say

            if left(purchase_order.value) = "EPI"
            someotherfield.visible = .t.
            end if

            and the onfetch event of the form to say

            someotherfield.visible = .f.

            so that the visibility of the field is set to false for the next record.
            Last edited by Stan Mathews; 05-14-2006, 09:33 PM.
            There can be only one.

            Comment


              #7
              Originally posted by Stan Mathews
              This probably has some significance to you but doesn't provide us with enough information to guide you.

              Do you mean to say that only purchase orders that have the "EPI" prefix will need the other field? Do you mean to say that any purchase order that doesn't have the "REG" prefix will need the other field?

              You can program any logical condition you wish into the display of the other field but you must be able to express that condition in logical terms.

              You could use the ondepart event of the purchase order field to say

              if left(purchase_order.value) = "EPI"
              someotherfield.visible = .t.
              end if

              and the onfetch event of the form to say

              someotherfield.visible = .f.

              so that the visibility of the field is set to false for the next record.
              Ah, I see. I've done some scripting in other programs, but not alot. I'll have to have someone work with me on that. Thank you both for your help :) You've definitely pointed me in the right direction.

              Comment

              Working...
              X