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

fetching the next child record

  • Filter
  • Time
  • Show
Clear All
new posts

  • fetching the next child record

    Ok.. new problem... I have a form (MAIN).. its parent table is Clients

    it has a subform (SUBFORM1), whose parent table is Plaintiffs.

    I have 2 buttons I want to use to page the subform through the child records. These buttons MUST reside on MAIN.

    I can get the buttons to page through the parent records on MAIN,, but thats not the desired result. I need the buttons to page the subform records..

    This should be simple... but I just aint gettin it.

  • #2
    RE: fetching the next child record

    From the Help files...

    ]This script is attached to a button. It moves to the next record in the embed browse (called Items) on a form:


    I hate to say this but I haven't tried it on a subform. My guess is that it should work. Let us know.


    • #3
      RE: fetching the next child record

      nope.. tried it again anyway.. but I had already tried that ...

      I can put the button on the form (Plaintiff)in the subform (SUBFORM1)and it works... changes the child record

      parentform.fetch_next()... a real no-brainer
      plaintiff.fetch_next()... works as well

      but when I move the button and change the code to address the subform... it changes the parent instead of the child..

      this is what I tried:

      :MAIN:SUBFORM1.fetch_next() .. this changes the parent.

      So I am perplexed. (another word for tired... lol)


      • #4
        RE: fetching the next child record


        tbl2 = table.get("childnamehere")
        AlphaBase Solutions, LLC

        [email protected]


        • #5
          RE: fetching the next child record


          I think as long as the buttons are on the Parent, you won't get them to work on the subform. I presume you're talking about buttons that advance to the next or previous record?
          Why MUST the buttons be on the parent? Why can't you put buttons on the subform which WILL work the child records?

          TYVM :) kenn

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


          • #6
            RE: fetching the next child record

            you have to set focus to the subform before the fetch_next(). this should do it:



            • #7
              RE: fetching the next child record

              The buttons to fetch the next child record reside on the parent form to allow easy navigation of the child records without unlocking the form. At the request of the client the form, including the subform, is locked to prevent inadvertent record editing... placing the search and navigation buttons on the parent form allows these buttons to work without unlocking.

              I will try the focus change idea next.. I didnt try that earlier.


              • #8
                RE: fetching the next child record

                Well... tried it but that didnt get it either... so I presume the lock is whats keeping it from working.. I dont know.


                • #9
                  RE: fetching the next child record

                  >>At the request of the client the form, including the subform, is locked to prevent inadvertent record editing.


                  • #10
                    RE: fetching the next child record

                    Here is the "locking" code set to the forms ONINIT:


                    I presume the subform1.disable is whats stopping me in my tracks.. going to undisable it and see if I can get the buttons to work then.


                    • #11
                      RE: fetching the next child record

                      Tried that too... wont do it.


                      • #12
                        RE: fetching the next child record

                        Well... its the lock thats keeping it from working alright.

                        As soon as I enabled the subform the buttons behave.. so now I know what to do

                        Thanks a million.. this is the greatest.


                        • #13
                          RE: fetching the next child record

                          Well.. fixed one problem but it introduced another...

                          I enable the subform to allow the fetch.. and the fetchs work fine.. but it leaves the child record unlocked sooo.. I relock it after the fetch...but then it goes right back to displaying the first child record... lol

                          Doesnt appear there is a way to keep em locked out AND let em navigate. Not on the subform anyway.

                          Any ideas anyone?


                          • #14
                            RE: fetching the next child record


                            I was resynching after I relocked the form... this forced the child to revert back to the first child record.. form was locked tho so the relock code worked.

                            So instead of resynching.. I set focus back to parent form after relocking.. works as planned.. the button will now unlock the subform, do the fetch next or prev, relock the subform and set focus back to the parent.. the child record that was fetched is displayed.. and its locked... all is well!

                            Thanks again to all who replied!