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

Why does the record save when I have not pressed 'save' / F9?

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

    Why does the record save when I have not pressed 'save' / F9?

    Good day,

    I have noticed that when entering a new records data, when all the fileds on the form has been populated, the record saves automatically without the user pressing 'save' or F9.

    I would like to disable this feature in A5, i.e I want the user to press F9 to commit. Please advise how to do this?

    Kind regards
    George

    #2
    Re: Why does the record save when I have not pressed 'save' / F9?

    for the record, I would live with it. But ...

    say the table name is "mytable"
    in your autoexec script, dim a global logical variable
    dim global mytablecan as L=.f.
    then in the table's, field rules', cansaverecord event put

    Code:
    if a_deleting_record
         end 'don't fire when deleting
    end if 
    if mytablecan=.f.
         cancel() 'refuse save
         end
    end if 
    mytablecan=.f.
    then, depending on how you want to flag the record for saving

    like from a button, or from the F9 key you could put on your save button
    mytablecan=.t.
    parentform.commit()
    also, in the form's onkey code you can put
    Code:
    if a_user.key.value="{f9}"
         a_user.key.handled=.t.
         if a_user.key.event="down"
              mytablecan=.t.
              parentform.commit()
         end if 
    end if
    if you have a set, and the child records are in an embedded browse, and you want this functionality there, too, it would be more complex.
    Last edited by martinwcole; 10-15-2007, 03:07 AM.
    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

    Comment


      #3
      Re: Why does the record save when I have not pressed 'save' / F9?

      Martin, would you then call this 'automaticall saving' a feature? Ie is this functioning as expected?

      George

      Comment


        #4
        Re: Why does the record save when I have not pressed 'save' / F9?

        yes and no
        it is not automatic to save when all fields are entered, necessarily, as far as I know

        usually what triggers the save is entering data for the last item in the tab order, for example, which would have it fetch to a different record. Anything which would cause it to fetch will normally save the current record before moving to the next or prev

        why do you want to disable the feature?
        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

        Comment


          #5
          Re: Why does the record save when I have not pressed 'save' / F9?

          Martin,
          My users are not comfortable with this function, they want to be in control :)

          Based on what you have told me, I am going to try and persuade them that we do not fiddle with this, and keep as is.

          Maybe it was the fact that nobody (including myself) knew when the trigger fired. Now I am in a stronger position to discuss this functionality with them.

          George

          Comment


            #6
            Re: Why does the record save when I have not pressed 'save' / F9?

            From the Help file topic "Using a Form" in the User's Guide:
            Saving Records

            Changes you make to a record (including entering a new record) are saved when you leave the record. For example, if you change a field value and press the Next button, Alpha Five saves the changes you made to the previous record.

            To save changes while viewing a record, click the Save Record button on the toolbar or press F9.
            When the user tabs through the last field (in tab order) Alpha fetches the next record. The same thing happens when the user moves to a different row in an embedded browse. In a set based form where child table records are displayed in an embedded browse the same thing happens when the user shifts focus from a row in the embedded browse to a field in the parent table. The pending edits will be saved for you. This surprises folks who assume that data entry is form based. It's not. Data entry is based on records in individual tables.

            George, if your data entry form is based on a single table a useful trick to prevent Alpha Five from fetching the next record (and thereby automatically saving the pending edits) is to place a dummy field on the form and arrange it to be last in tab order. In the dummy's onArrive event place a script that will shift focus to the field that's first in tab order. Now, when the user tabs through the last "real" field focus shifts to the dummy, and then immediately shifts to the first field. The effect is to enable the user to tab through all the fields in the current record over and over without navigating to the next record. Once you have it going you can change the properties of the dummy field so that it's invisible and the user won't be the wiser.

            Comment


              #7
              Re: Why does the record save when I have not pressed 'save' / F9?

              George,

              This help topic may be of help. Circular Tabbing on a Form

              Edit: OOPS Had walked away thinking I had presssed submit. Found I had not and then did only to see Tom already answered. The help topic I referenced is what Tom is speaking of in his last paragraph.
              Tim Kiebert
              Eagle Creek Citrus
              A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

              Comment


                #8
                Re: Why does the record save when I have not pressed 'save' / F9?

                Thanks for the tip Tom, now that wil help a lot.

                Regards
                George

                Comment

                Working...
                X