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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Prevent page down past last record

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Prevent page down past last record

    If a user is paging down through records and arrives at the last record, by index or record number, the next page down starts to add a new record.

    I would like to prevent this. I'm not sure if eof() is the key. I've tried several things related to reading eof(), but I'm not sure at what point it reads the new record as eof(). I've tried record events CanEnterRecord and OnEnterRecord but just couldn't make it work.

    Do you know the best way to do this? Thanks.

    Jeff
    Tags: None
    #2
    Re: Prevent page down past last record

    Originally posted by Jeff Fried View Post
    If a user is paging down through records and arrives at the last record, by index or record number, the next page down starts to add a new record.

    I would like to prevent this. I'm not sure if eof() is the key. I've tried several things related to reading eof(), but I'm not sure at what point it reads the new record as eof(). I've tried record events CanEnterRecord and OnEnterRecord but just couldn't make it work.

    Do you know the best way to do this? Thanks.

    Jeff
    I forgot to mention that I also tried the OnKey form event. This might be the way to do this but I'm not sure it's the best.

    Jeff

    Comment

      #3
      Re: Prevent page down past last record

      Where are they paging down?

      If your're speaking of a form, edit the form's properties, Form tab, Restrictions, check Continuous Enters.
      There can be only one.

      Comment

        #4
        Re: Prevent page down past last record

        Yes, it is a form. I did as you said, checking Continuous Enters, then positioned myself on the last record, and it allowed me to page down and thereby entering a new record.

        Does this work on yours but not on mine?

        Jeff

        Comment

          #5
          Re: Prevent page down past last record

          No, just working from (faulty) memory.

          I think you'll have to completely Restrict Enters and add a new record button (action script element).

          Button with

          topparent.Restrict_enter = .f.
          topparent.new_record()
          topparent.Restrict_enter = .t.

          should do it.
          Last edited by Stan Mathews; 01-17-2014, 04:51 PM.
          There can be only one.

          Comment

            #6
            Re: Prevent page down past last record

            Jeff,

            Like Stan, I'd forgotten that pgDn wasn't "restricted" in the same way tabbing through the last field on the form gets "restricted".

            I think a complicated system could be constructed using the onKey event, assuming you were talking about the primary table supporting the form, and assuming a permanent index controlled the sort sequence, and assuming you did not permit queries that might change the range or sort sequence of the displayed data. But, the "cure" is worse than the "disease".

            What specific problem are you trying to solve? If a new record is begun by mistake, can't it be canceled easily? Are you winding up with empty records or what?

            Comment

              #7
              Re: Prevent page down past last record

              Since Alpha came up with parent-modal a number of years ago, (with which I have always had issues,) I make all forms modeless, and at the onfetch event I say parentform.allow_change(.f.)
              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

                #8
                Re: Prevent page down past last record

                Originally posted by Stan Mathews View Post
                No, just working from (faulty) memory.

                I think you'll have to completely Restrict Enters and add a new record button (action script element).

                Button with

                topparent.Restrict_enter = .f.
                topparent.new_record()
                topparent.Restrict_enter = .t.

                should do it.
                Stan,

                The solution appears to be putting the restriction against enters on the form then releasing the restriction when the button to add a new record (new order, in this case) is clicked.

                I put your code in and it does allow the entry of a new record. For some reason the "topparent.restrict_enter = .t." didn't work since after I escaped from entering the new form I was able to page down to a new enter. I'll have to play with it some more.

                Tom, the purpose for this, to answer your question, is to keep the adding of new orders under the control of the new order button and not have users inadvertently bring up a new order screen when paging down past the last record. There is a quality control procedure I'm putting in place, and the QC manager will be able to click a button to filter and sort on the orders that need to be QC'd. A checkmark on the form (only accessible by the QC manager) is checked when QC passes. So the QC manager will just page down through the pending QC reviews, and I want to prevent going past the last record to be QC'd. This is why I want to employ the prevention against the enter after the last record. The default restriction against enters on the form appears to be correct. Now I just need to figure out why the xbasic to re-employ the restriction after removing the restriction did not work.

                Thanks to all.

                Jeff

                Comment

                Previous template Next
                Working...
                X