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

why, when finding a record, it doesnt stop on reco

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

    why, when finding a record, it doesnt stop on reco

    Why is it, that when we do an index or query, and we find by key, that when it stops, it is not on the record, but on the record after it.
    Tags: None
    #2
    RE: why, when finding a record, it doesnt stop on

    Rebuild the indexes for the table. Compact the database and then try.

    Comment

      #3
      RE: why, when finding a record, it doesnt stop on

      chuck:

      When you find by key if there is no match the search stops on the next logical record.


      I hope this helps.

      bob adler

      Comment

        #4
        RE: why, when finding a record, it doesnt stop on

        I have a customer with a similar problem that is NOT related to the index or missing records. The bad news is that we haven't figured out a solution that doesn't involve simplifying the set.

        The set is fairly complex and involves 4 one-many child/grandchild/great-grandchild tables as well as 6 one-one relationships. Everything worked fine until the last one-many relation was added at the lowest level. Now, 'finds' that used to work, and are based on only the top parent table, will now end up on the record after the desired record. However, if you watch the form, it first goes to the correct record then jumps down to the next record.

        I first thought this had to be something in the field rules or form but deleted all the field rules and used the default form with the same results. Removing that last one-many relationship returns 'normal' function.

        Our solution was to remove that final relationship and provide a button on the form for showing the add'l data from that table.

        I plan to investigate further when and if time permits.

        Does your situation involve a similarly complex set?

        Comment

          #5
          RE: why, when finding a record, it doesnt stop on

          There is a match, after it finds, if you hit page up, there it is

          Comment

            #6
            RE: why, when finding a record, it doesnt stop on

            Indexs are rebuilt each day, and we can not compact the database as it consistantly blows up the fpt files to 1 and 2 gig in size

            Comment

              #7
              RE: why, when finding a record, it doesnt stop on

              yes it does involve a complex set. the bad news is that this set was created in ver 1. and has worked fine for 6 years, we had to upgrade the computers to ME, so we had to upgrade the alpha, and i am forced to rewrite the scripting and convert the files and sets. the problem is, that it seems to do it on simple sets and single databases as well as complex sets

              Comment

                #8
                RE: why, when finding a record, it doesnt stop on

                I have never seen this on simple sets or, especially, individual tables unless there was something in the field rules or form events.

                If it is happening on individual tables, I would make a copy with no field rules and run from the default form. If this works, add field rules one at a time until you find the problem.

                Comment

                  #9
                  RE: why, when finding a record, it doesnt stop on

                  do you have any onkey scripts - if so, carfully check

                  Comment

                  Previous template Next
                  Working...
                  X