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

Jumping Records

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

    Jumping Records

    I have a set with the parent to be INVOICE=>ITEMS
    As you can see it is one to many. On the form I have the Invoice data on the top of the form and the Items in a browse. My problem is if I only have ONE item in the browse. When making a change in the invoice section of the form, once the change is started all of a sudden A5 goes to the next record and the change is being entered in the wrong record. For a temporary fix, I am entering a second record (bogus) in the browse. Another temp fix is to do a quick filter on the invoice number. But after I do a print from a button on the form, A5 returns to the wrong record.

    I have tried recreating/rebuilding indexes, db compact. NOthing. In fact it even happens with the default form.

    Any ideas...
    Tags: None
    #2
    RE: Jumping Records

    Hello Philip,

    Are you saying that as soon as you start changing an existing record, the form 'jumps' to the next record IF you only have one child record in the browse. If you have more than one record in the browse the form works as it should? This sounds really strange. Do you have any actions defined in the form or table events? Sounds like you have an event firing, although I can't understand what difference the records in the browse would make. You might fire up the debugger and make sure it is set to trace into next script, then go ahead and play with the form and see if the debugger brings up some code that might help explain what's going on.

    Good luck,
    Jim

    Comment

      #3
      RE: Jumping Records

      Hi Phil,

      Got to thinking after I'd answered you, this is a long shot, but how is your link between the parent and child defined? Is the linking field set to autoincrement? Is this on a network? I've seen some 'jumping around' before that is related to the autoincrementing of linking fields where you might have some strange values in the link field and more likely, blank values, causing problems. This however usually manifests itself by 'phantom' child records, but I have seen the parent record 'jump' around while in the browse where there is linking field problems.

      Good luck,
      Jim

      Comment

        #4
        RE: Jumping Records

        You are correct on what is happening. Mind you that there some other tables in the set but they are after the ITEMS table. I felt they would not have any factor in the equation. There are no events for a change. I do some events when saving the record.

        Comment

          #5
          RE: Jumping Records

          The link is by the field invoice_num and it is one to many from INVOICE to ITEMS. There is no autoincrement and yes it is on the network.

          Comment

            #6
            RE: Jumping Records

            Philip,
            This is a something of a longshot, but do you have a resynch() anywhere that might fire during data entry, either on the form events or a field rule event? This has caused me some problems in the past. Also, how is your invoice_num generated? Is it user entered or is there some other method that might be creating a new invoice number unexpectedly? I recently ran into a problem with a script that creates a new item_no in an inventory app. I forgot to limit the creation to only the enter mode. Everytime I tried to edit the parent, a new number was generated.

            Jerry

            Comment

              #7
              RE: Jumping Records

              Jerry,

              There is no resync and I purposely stayed away from autoincrement for the invoice number. It is manually input.

              Question: if you have a set like this
              invoice (parent)
              =>items (child1 one to many (to invoice))
              ->acctsrec (child2 one to one (to invoice))
              =>arledger (child3 one to many (to acctsrec))
              ->customer (child4 one to one (to invoice))

              Could any of the child tables after ITEMS be a problem?

              Comment

                #8
                RE: Jumping Records

                Philip,
                The fact that the problem also occurs in the default form would seem to indicate a corrupted index, a field rule problem, or corrupted data. One way to check this would be to duplicate both the parent and the child to new tables without supporting files, just the records. Then create a new set with the same link and see if the problem still exists. If it doesn't, try recreating every other index, one at a time, and then add field rules for each, one at a time. If that works, then try copying all forms, browses, etc. If all goes well, duplicate the tables back to the original names.

                This seems like a lot of work, but sometimes it is the only way.

                Jerry

                Comment

                Previous template Next
                Working...
                X