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



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

Stop Tab When...

  • Filter
  • Time
  • Show
Clear All
new posts

  • Stop Tab When...

    Hi folks,

    I have a form with 8 tabs on with a browse on each and the first field of the browse is a table lookup. I need to stop a tab being selected if its lookup is empty.
    I know that tabs have canchangetab action scripts but how would I tell A5 to not allow entry if lookup empty as lookup is set on 1st item in browse?
    Thanks for any ideas(much appreciated)

  • #2
    RE: Stop Tab When...

    I made it a rule, about two years ago, to never never never have either the first or last field on a form or embedded browse be a lookup field. It caused me nothing but problems.
    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


    • #3
      RE: Stop Tab When...


      I am interested to read about your experience. I do use a field in an embedded browse (on a tabbed object,yet)which has a lookup but I do not have it set to automatically pop up. Is that what is saving me?

      What sort of problems do you get?

      Bill Hanigsberg


      • #4
        RE: Stop Tab When...

        Hi guys,

        The fact that the 1st field is a lookup is not a problem - or hasn't been so far (fingers crossed) its just that I have no idea how to script it to check if a FIELD RULE LOOKUP is blank or not so I can then say dont change tab if empty.

        Any ideas



        • #5
          RE: Stop Tab When...

          I could be wrong here, but I don't think there is a canttabchange event. That is probably what it would take to easily disallow the entry to a tabbed screen based upon zero records in a particular table. That being said, you might be able to do a check on whether or not a table has any records ( based on the parent ) and put a read only property to that field that has a lookup field rule. If you are using what many do, a hidden object to advance to the next tab, you could code it to skip a tab because it has no valid records in a particular table. This might slow down navigation, records_get(), but basically do what you want. Unless you code the entire form with variables, I don't think you'll achieve exactly what you want,but you may come close.


          • #6
            RE: Stop Tab When...


            Thanks for the reply, there is a CANTABCHANGE event on a tabbed item which I have used before (V4.5 build 266) to say if a field is blank dont change tabs.

            But I am not sure what the script would be to check a lookup is blank or not (the lookup is based on field rules with a filter).



            • #7
              RE: Stop Tab When...


              There are two different ways to check if a filtered group of records includes any entries. If the number of different lookups are small, you can create an index for each different filtered lookup. It the number of lookups is large or is based on a variable or a value that may be unique, you can create a query. In either case, you can then use .reocrds_get() to determine is any records fit the criteria. As an example, if the lookup uses an index called "lookup1" and the lookup table is called "myfile", this would work.

              dim recs as n

              tbl ="myfile")

              idx_org = tbl.index_primary_get() ' Need this to reset the index back to current

              idx = tbl.index_primary_put("lookup1") ' you could but a query here and assign the idx pointer to the query. i.e. idx = tbl.query.create()

              recs = idx.records_get()

              if recs = 0
              ui_msg_box("Lookup","No records found")
              ' Whatever you want to do if lookup is blank
              end if



              • #8
                RE: Stop Tab When...

                Thank you Jerry,

                Thats just the pointers I need to solve my problem.

                Thankyou for your time and effort.