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

Confirming Change

  • Filter
  • Time
  • Show
Clear All
new posts

  • Confirming Change

    I would like to ask the user if they wish to save changes to a record if they attempt to close a form or fetch a new record. I have been toying with the AskSaveChange, OnFetch, and CanExit events for forms but can't seem to find the right combinations to keep the user from accidentally changing a record. I want to keep the forms as "modeless".

    Thanks for any tips,


  • #2
    RE: Confirming Change

    Rhett, Why don't you just restrict all edits after a record is initially saved and require the user press an
    'Allow Edits' button be able to make changes. This will force anyone wishing to make a change to press the button before changing the record and thus, avoid accidental changes.


    • #3
      RE: Confirming Change

      This has been presented as an option but rejected by the users (they have good reasons). I feel there must be a way to do what I am looking for, I just have not found the right combination yet. I see this functionality in other software such as QuickBooks and it is very useful.



      • #4
        RE: Confirming Change

        i don't believe it's possible to do what you want to do.
        the askcansave event and the cansave events don't fire when the
        user simply moves focus to another record after making a
        change. the onfetch event does fire butit fires
        after the change has taken place. if you figure out
        a way to do it, let us all know, but i spent a lot of time
        on that one and don't think it is possible.
        - peter


        • #5
          RE: Confirming Change

          oops, i made a mis-statement there. i believe the cansave
          event does fire when the user moves off a changed
          record on a form, but not on a browse. therefore if you
          do not show any browses on your form, you can accomplish
          what you want. if you have a browse on the form you can't
          intercept the user if an inadvertent change is made to a record
          on the browse.
          to answer this problem, the designers of a5 have added
          a CanRowChange browse event to v5.
          - peter


          • #6
            RE: Confirming Change

            Dr. Wayne,

            Get news! However, I have been toying with this event and I can't get the results I am after. 90% of the forms do not have embedded browses. How can I "roll back" the changes if they indicate that they do not want to save their changes?



            • #7
              RE: Confirming Change

              I played around with those events too and I found that it gets very messy. I have adopted Peter Wayne's general methodology of using filtered dialogs of child tables to enter & edit data. I disable the system menu and use a close & cancel button. New records are entered by xbasic (basically a blank record) and then edited in the dialog. If the record is left blank, the close button deletes the record authomatically. Personally, I have found this a better method to control data input. The user can't move off the current record and it provides for a consistent & foolproof data entry method.
              AlphaBase Solutions, LLC

              [email protected]


              • #8
                RE: Confirming Change

                essentially you would need to put something in the cansave
                event to cancel the event if the user did not intentionally
                save the record.
                for example, you could have an OnKey event that checks
                for {F9} being pressed, and set a logical flag if
                {F9} was pressed. if {F9| was pressed then you can allow
                the save to take place, otherwise you cancel the save in
                the CanSave event and notify the user that all changes were
                lost, meanwhile clearing the value of the logical flag.

                (i haven't tried this exact method, by the way, but i think
                it should work. caveat programmator)

                - peter


                • #9
                  RE: Confirming Change

                  Here's a way (albeit somewhat complicated) to prompt the user to save the record when moving to another record using PGDN or the NEXT button in the toolbar.

                  First, I put the following script in the ONKEY event of the form:

                  dim global chg as n
                  f = topparent.this
                  if a_user.key.value = "{pgdn}".or.a_user.key.value = "{pgup}"
                  if a_user.key.event = "down" then
                  if mode="CHANGE"
                  chg=ui_msg_box("CHANGES HAVE BEEN MADE","Save changes?",32+4+256)
                  if chg=7
                  elseif chg=6
                  end if
                  end if
                  a_user.key.handled = ".t."
                  end if
                  end if

                  If the record is in change mode, the message will appear, with the default choice being NO (so he can press ENTER to continue and not save the changes). He will then have to press PGUP or PGDN again to go to another record.

                  Next, I designed a custom tool bar, and put this script in the NEXT button:

                  dim global chg as n

                  if mode="CHANGE"
                  chg=ui_msg_box("CHANGES HAVE BEEN MADE","Do you want to save your changes?",32+4+256)
                  if chg=7
                  elseif chg=6
                  end if
                  end if


                  This does the same as the script above, but has the advantage of going to the next record automatically (I couldn't get that to happen in the first script - maybe someone else can figure it out).

                  You would also put a similar script in the PREV button, as well as the FIRST and LAST buttons.

                  I tested it, and it worked as far as I took it. You should test it thoroughly in ALL possible modes to make sure it does what you want.