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

Conditional Objects and Enter/Change Mode

  • Filter
  • Time
  • Show
Clear All
new posts

  • Conditional Objects and Enter/Change Mode

    I'd like to be able to show or hide a button which copies data from a Patient Record into a Next of Kin Record.
    The button only needs to show when in Enter Mode for a New record, or the Current Record is in Change Mode, so I have out it in a Conditional Object.
    Having looked at and tried the tbl.mode_get() I am a little stuck.
    All ideas welcome.
    See our Hybrid Option here;

    If at first you don't succeed; call it Version 1.0

  • #2
    Re: Conditional Objects and Enter/Change Mode

    May I ask why you want to copy data that hasn't yet been saved? Seems backwards to me. What am I missing?


    • #3
      Re: Conditional Objects and Enter/Change Mode

      Mornin' Tom.
      The Patient Details include Address and telephone Number
      Where there is a NoK living in the same house, to save the telecon operator rekeying the same data, I'd like to have a button to copy previously entered - possibly unsaved data from the Patient to the NoK record.
      It works as intended in Tabbed Objects, but I'd like to be able to hide it if not in Change or Enter mode.
      Form Setup.
      Tab1 has a Browse to select a Patient
      Tab 2 has Patient demographics
      Tab 3 has NoK
      Tab 4 has Referral Information.

      If I enter or change data in a Patient record, (Tab 2), when I go to Tab 3, I can click the buton and set the fields in Tab 3 to those in Tab 2.
      Unfortunately it is not possible to have a simple "They live together" box due to Data Protection.
      See our Hybrid Option here;

      If at first you don't succeed; call it Version 1.0


      • #4
        Re: Conditional Objects and Enter/Change Mode

        My point is simply that until the user saves the pending new record or the changes to an existing record the data hasn't been changed. Even so you want to permit them to copy the information somewhere else? And then prevent them from doing so when the original edits are finished and saved? Sounds backwards to me. Sorry.


        • #5
          Re: Conditional Objects and Enter/Change Mode

          Let me try and explain it another way.
          I can easily put a "Save" in when moving from Tab to Tab, however, the presumption is that when a user changes Tabs, the data previously is correct.
          A "Save" between Tabs would make it "forwards" as opposed to "backwards". (Your comment).
          I still have the problem of showing or hiding a button based on the Form being in Enter or Change Mode, or no mode at all.

          Suppose you wanted to show a Conditional Object with the text "You are now in Data Entry Mode" - when a new record was being entered, or "You are now in Data Change Mode" when editing existing data.
          How would you do that?

          If I get it working as I want, I'll post the table and form.
          See our Hybrid Option here;

          If at first you don't succeed; call it Version 1.0


          • #6
            Re: Conditional Objects and Enter/Change Mode

            table.current().mode_get() = 0 'view mode
            table.current().mode_get() = 1 'change mode
            table.current().mode_get() = 2 'enter mode
            table.current().mode_get() = 3 'query mode
            table.current().mode_get() = 4 'find mode

            If you're working with a set you need to refer to the table being tested with the slot parameter for table.current().
            There can be only one.


            • #7
              Re: Conditional Objects and Enter/Change Mode

              Problem is Stan, I cannot get these into the Conditional Object "Conditions".
              I'll try creating some code (I hate that) to handle a Show/Hide.
              See our Hybrid Option here;

              If at first you don't succeed; call it Version 1.0


              • #8
                Re: Conditional Objects and Enter/Change Mode

                Works for me in v5, v8, and v10

                There can be only one.


                • #9
                  Re: Conditional Objects and Enter/Change Mode

                  And the end result.
                  Thanks Stan.
                  Tom, I apologise if my design seems a bit "pants" but it is based on the Alpha Sports Invoice idea.
                  Attached Files
                  See our Hybrid Option here;

                  If at first you don't succeed; call it Version 1.0


                  • #10
                    Re: Conditional Objects and Enter/Change Mode

                    Ted, no apologies needed.

                    I see that your conditional object is on the tab where the edits are occurring. And that your button on the CO retrieves the patient data from a previously saved record. I thought you were going the other way round. Editing the patient data and then copying it to another table before saving it. Sorry for the confusion this engendered.


                    • #11
                      Re: Conditional Objects and Enter/Change Mode

                      Did you look ath the result Tom?
                      See our Hybrid Option here;

                      If at first you don't succeed; call it Version 1.0


                      • #12
                        Re: Conditional Objects and Enter/Change Mode

                        Yes, why do you ask?


                        • #13
                          Re: Conditional Objects and Enter/Change Mode

                          Because I commented out the SaveOnTabChange, so the data in the Patient Tab is present but not committed
                          This means that if the User hits the Copy Button, and then goes back to the Patient Tab and does another change, without saving the record in between the data will be different.
                          To that end, I will probably put a Logical "NoK Same as Patient" tick box, and run a check when saving to make sure that the data is the same in the corresponding fields.
                          It's a bit of a nightmare, as the NoK might live in 21a, and the Patient in 21b the rest of the address is the same.
                          Ho Hum!
                          I've added a warning against the specific differences by Field where there is a Logical Check to say that the two are in the same habitation.
                          Last edited by Ted Giles; 07-02-2011, 05:18 AM. Reason: bit more work on this.
                          See our Hybrid Option here;

                          If at first you don't succeed; call it Version 1.0