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

Creating A Coontitional Object

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

    Creating A Coontitional Object

    Thanks to Gary Traub for his instructions in pointing me to the use of a contitional object instead of a tabbed object. He is right, I love it! Here's what Gary had to say:

    You can use as many layers as you want - and can easily put embedded browses or any other objects.

    All you need to do is this:

    1. Create a layout variable called say condtest as n

    2. Use the toolbox to create a conditional object on your form.

    3. The object by default will be called cond1.

    4. Right click on it and define as many layers as you want. For example,
    condtest=1 Ledger
    condtest=2 Enter Charge
    condtest=3 Enter Payment

    5. Once you have defined the layers as described in step 4, then go ahead and put whatever objects you want on each layer. To do that, right click on the conditional object and you will see the layers you just defined. Select each in turn to place the fields, browses, frames, etc that you want on each layer.

    6. Now all that is left to do is to place buttons to select the various layers. In this example, you could have 3 buttons labeled: Ledger, Enter Charge, and Enter Payment. Each button would have the following code:

    For the "Ledger" button:

    condtest=1
    cond1.refresh()


    For the Enter Charge button:

    condtest=2
    cond1.refresh()

    For the Enter Payment button:

    condtest=3
    cond1.refresh()

    This may seem complicated or like a lot of work, but after you do it once or twice, it's very easy, and I really believe you will love it.
    -------------------------------------
    Here's what I figuered out and Gary concurred:

    If you want the conditional object to act like a tabbed object, you can use buttons to emulate the tabbed object. Else, you can use contitional statements on a field to activate a certain layer. There are many possibilties, thanks to Selwyn and his crew.

    To tab from layer to layer and begin with the first field in the tab order for that layer , that's just as easy. You do not need to set the tab order for all the layers as in 1 through 36. You only need the tab order in the sequence you would like for that layer. As a matter of fact, it really makes no difference what layer is next as you can use this code to go to whatever layer you wish. Thus the use of a conditional statement on a field in layer 1, could take you to any layer.

    This code goes on the last field (OnDepart event) in the tab order:

    condtest=2
    cond1.refresh()
    field_name.activate()

    Hope this is of help. Email me if you get stuck.

    kenn
    TYVM :) kenn

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

    #2
    RE: Creating A Conditional Object

    There, I spelled it right.
    TYVM :) kenn

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

    Comment


      #3
      RE: Creating A Coontitional Object

      I discovered this technique in version 4. But there was a bug in how the tab order worked. I would set the tab order to go from a field on the form to a field on the conditional object. Which field on the conditional object depended on the active layer, which was in turn set by the value entered in a previous field. I have layers for Labor (start and end times, to get a quantity), Materials (purchasing info on vendors, discounts, markups, etc), equipment and subcontractors. Which layer was active was set by the item code entered.

      Anyway, it didn't work right and I had to do some xbasic to make it it all work. I haven't looked, but is this fixed in version 5?

      And yes, it is very cool. Very efficient use of screen space. Very intuitive for data entry.

      Comment


        #4
        RE: Creating A Coontitional Object

        I've had no problem with the tab order. If anyone does, send me an email and we'll figure it out.

        kenn
        TYVM :) kenn

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

        Comment


          #5
          RE: Creating A Coontitional Object

          Kenn
          here is a sample that uses a slightly different approach to conditional objects. Open the Database for Stu_data and select the grade entry by student button (Period one is the only one with data) As you change quarters you will see a change in the display. --there is a hot spot to right of the title on the main menu to take you to the control panel

          Comment

          Working...
          X