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

Read past end of file

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

    Read past end of file

    I have the following expression:
    if(Criminal>Crimestatus="convicted","Red", " ")
    When clicking evaluate in the expression builder, the following message appears: Read past end of file

    What does it mean? and how do I solve the problem?

    Thanks,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    RE: Read past end of file

    The most frequent cause for this is that you're evaluating an expression while building a form, but you have no records in your table. Put a few records in and you won't get the message.

    - Steve
    -Steve
    sigpic

    Comment


      #3
      RE: Read past end of file

      Is that verbatim?


      if(Criminal>Crimestatus="convicted","Red", " ")
      should be:if(Criminal->Crimestatus="convicted","Red", " ")

      So much easier to catch typos than create your own code, but hard to see your own typos because you "know" what you "meant" to type.
      There can be only one.

      Comment


        #4
        RE: Read past end of file

        Steve & Stan,

        Thanks, I'll get a few records in. However, I did enter one record and set the crimestatus field to conviction. It didn't change color and when after leaving the database and entering again, the crime status field was empty. I suspect that has something to do with it but now it's to figure out what causing the field to not store data. The field is a dropdown list box set on the crimestatus field. Yes, I did see the difference bewteen your expression and mine. Mine is the same as yours. When I copied it to the message board, I accidently deleted the "-".

        Any thoughts why the data won't stay?

        Thanks, Ken
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment


          #5
          RE: Read past end of file

          Ken, it sounds as though your immediate situation has been diagnosed. However, I've encountered this error in another context, so I thought I'd write it up.

          If one deletes a record from the parent table in a set, but do not use referential integrity to cascade the delete to the related child records, you wind up with "orphan" records in the child table. i.e. child records that don't have a related parent record.

          In many instances this is harmless...just a waste of disk space. However, I run some reports against the same tables using a different set definition. In the new set, I invert the original order of the tables, so that the former child table now becomes the parent, and the former parent is now the child. As my report runs, it pulls records from the parent table, and "looks up" fields from the new child table. My report design *assumes* that there will always be a child record related to each parent. However, since some of the parent records were "orphaned" by the earlier deletetion this isn't always true. When a missing child record is encountered the report throws the same error message you hit.

          I've found that its possible to test whether a child record is present or not using the exist() function, and use this in all my set based reports whenever my report pulls records from two or more tables.

          -- tom

          Comment


            #6
            RE: Read past end of file

            Tom,

            Thanks for the reply. Your write up is good to keep in mind. I appreciate your thoughts.

            ken
            TYVM :) kenn

            Knowing what you can achieve will not become reality until you imagine and explore.

            Comment

            Working...
            X