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

Reading the last record of a text file

  • Filter
  • Time
  • Show
Clear All
new posts

    Reading the last record of a text file

    As quickly as possible I would like to read the LAST record of a text file. I have written a script that opens a text file that has about 10,000 records. I can iterate through the file until I retrieve the last record but this is slow. What I would really like to do is open the file and immediately read the last record of the text file. I know he layout of each record. I know the length of each record too. It would seem that I would just need to do a calculation to set my file pointer to the beginning of the last record and then read the record but I can't figure out if this is possible with A5 and furthermore the correct commands to use.

    If someone could give me a nudge in the correct direction that would be great!

    Thank you,


    Re: Reading the last record of a text file

    CP (real name?),
    A text file (as far as I know) does not have records. It can have lines. If this is what you mean then maybe one of these functions will work---check them out in the help file

    Reverses a delimited list of entries.
    Reverses the order of a CR-LF delimited list.
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau


      Re: Reading the last record of a text file

      CP, In order to move a pointer to the "last" line wouldn't you first have to know how many other lines there are to skip over?

      I think the line_count() function will give you the total number of lines in the file, if your text file uses cr-lf line delimiters.

      With the line count, and assuming a fixed width on each line, you could compute the number of bytes to "jump over" from the beginning of the file, if you remember to include the cr-lf pairs at the end of each line. You could then use <file>.seek() to jump to the beginning of the last line, and <file>.readb() to read the bytes in the last line.

      This sounds like the approach you were looking for. Not sure it will be faster, but thought I'd mention it.


        Re: Reading the last record of a text file

        I was working on something similar to your suggestion while you posted.

        I used line_count to get the lines and then the stringscanner object to get the text of the line corresponding to the line count. A file that has 980,000 lines took less than three seconds

        dim text_lcv as C
        Dim LastLine_lcv as C
        dim lines_lnv as N
        dim ss_lpv as P
        text_lcv = file.to_string("E:\My Documents\gcp\Grader logs\Logs\20090710.log")
        lines_lnv = line_count(text_lcv)
        ss_lpv = stringscanner.Create(text_lcv)
        LastLine_lcv = ss_lpv.GetLineText(lines_lnv)
        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.