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

Last Record Test

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

    Last Record Test

    Hello All,

    I have a small script that runs off a button on a form. The purpose of the script is to take the values on the form and populate various tables, and move to the next record on the form. All this works okay the problem I have is how to I prevent the next record action if the current record is the last in the table. This is a problem as there is an autoincrement field in the table behind the form and if it goes past the last record a new empty record with just the autoicncrement field poulated.
    I guess I'm going the long way about asking how can I check if the current record I'm in on the form is the last in the table??????
    As always thanks in advance.


    Cheers
    Tom

    #2
    RE: Last Record Test

    Wouldn't this be a good place to use the

    while .not. "tbl".fetch_eof()

    "your commands here"

    end while


    which should cease processing if the next record is the end of file marker.
    There can be only one.

    Comment


      #3
      RE: Last Record Test

      Hello Stan,

      Thanks for the quick response.
      I'm sorry I don't fully follow, I don't really won't to fetch through all the records in a table, I just want to see if the current record is the last in either the query list, or the table, and if it is skip the command to fetch the next record (which end up creating a new record).

      Cheers
      Tom

      Comment


        #4
        RE: Last Record Test

        How about, early in your script, after query or whatever, you "tbl".fetch_last(), capture that record number (recno()) to a variable, go back to the first of the records to be processed("tbl".fetch_first()), begin processing - having enclosed the "tbl".fetch_next() command in an

        if .not. "tbl".recno() = "the value found to be the last record, per above" then

        "tbl".fetch_next()

        end if

        This should work for any index or query, I think.
        There can be only one.

        Comment


          #5
          RE: Last Record Test

          Hello Stan,

          Thanks for the suggesetion, unfortunately left the office now, will give it a try in the morning and let you know how I get on.
          Still a bit confused as the records are selected by a filter form that then opens the other form and has the query run at that stage. I am sure (hopeful!!) that if I play around with the suggestion you've given me I'll ge there.

          Once again many thanks

          Cheers
          Tom

          Comment


            #6
            RE: Last Record Test

            Hello Stan, and All

            Thanks for all your help although I think I led you up the garden path so to speak. I was just about to start working on your suggestion when it came to me that all I needed to do was to use the forms properties and click on the Enter new Record Restriction. Its not the first time I've got lost looking for the difficult solution to an easy problem, still it is happening less.
            Again thanks for your advice.


            Cheers
            Tom

            Comment


              #7
              RE: Last Record Test

              I just assumed you had a reason this couldn't be the case.
              There can be only one.

              Comment

              Working...
              X