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

Remain on current dialog record

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

    Remain on current dialog record

    I am off track and need some help.

    I have a dialog which always moves to another record when I click 'save', but I want it to remain on the current record.
    I am pretty sure it does this because of getting the primary key after saving, as seen here:

    ExecuteServerSideAction("Save Data::SaveIt")
    ExecuteServerSideAction("Get Primary Keys for Parent Table::LoadKeys")

    But if I remove the 'loadkeys', I get this error when I edit a repeating section of a current record and try to save it.
    "Record not found. After Executing SQL SELECT to refresh row in section"

    There is something I am missing, so I hope someone can point me in the right direction.
    J.R.
    Epigate Software, LLC.

    [email protected]
    http://www.epigate.com
    sigpic

    #2
    Re: Remain on current dialog record

    Bump

    How is everyone saving records in a dialog and make is stay on the record just saved?
    J.R.
    Epigate Software, LLC.

    [email protected]
    http://www.epigate.com
    sigpic

    Comment


      #3
      Re: Remain on current dialog record

      J.R.

      You set that in the ServerSide AfterDialogValidate action for Submit. Set the AfterSubmit Action.

      AfterSubmit.jpg

      Stephen
      Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

      Comment


        #4
        Re: Remain on current dialog record

        Thank you Stephen. I set it to "Edit record just submitted" but it still jumps to the first record after i click submit.
        This is where i really get confused. If i leave this code out:
        ExecuteServerSideAction("Get Primary Keys for Parent Table::LoadKeys")
        it saves and stays on the same record, but then it throws this error
        "Record not found. After Executing SQL SELECT to refresh row in section"
        So what do i need to do to complete the submit, stay on the same record without throwing the error?

        Seems so simple, but I have been wrestling with this for a few days without success.
        J.R.
        Epigate Software, LLC.

        [email protected]
        http://www.epigate.com
        sigpic

        Comment


          #5
          Re: Remain on current dialog record

          J.R.,

          Well, I'm not familiar with ExecuteServerSideAction("Get Primary Keys for Parent Table::LoadKeys")

          but I'm assuming you also have ExecuteServerSideAction("Save Data::Save_Order").
          This is where you would choose to Edit Record Just Submitted.
          This action script works fine for me here.

          Stephen

          Nevermind, I just re-read your original post.
          Last edited by iRadiate; 03-19-2012, 10:52 AM.
          Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

          Comment


            #6
            Re: Remain on current dialog record

            J.R.,

            Have you sorted this out?

            Do you have ExecuteServerSideAction("Get Primary Keys for Parent Table::LoadKeys") placed in the OnDialogInitialize event?
            And the ExecuteServerSideAction("Save Data::Save_Order") placed in the AfterDialogValidate event?

            Stephen
            Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment


              #7
              Re: Remain on current dialog record

              Thanks for following up Stephen.
              Still have not sorted out the problem. I do have what you listed above. And if i leave out the loadkeys after saving, the record is saved and remains on that record (just what i want to do), but, when i edit any field in the repeating section and click save, i get this error "Record not found. After Executing SQL SELECT to refresh row in section".

              There

              Since there is nothing on the board about this, i can only assume it is isolated to me and some bone-headed thing i have done.
              J.R.
              Epigate Software, LLC.

              [email protected]
              http://www.epigate.com
              sigpic

              Comment


                #8
                Re: Remain on current dialog record

                I am still having the error when saving an edit in the repeating section. The repeating section consists of only one field and it is a drop down. If i change the value in that drop down and click submit i get the error: "Record not found. After Executing SQL SELECT to refresh row in section"

                I have ExecuteServerSideAction("Get Primary Keys for Parent Table::LoadKeys") placed in the OnDialogInitialize event
                and the ExecuteServerSideAction("Save Data::Save_Order") placed in the AfterDialogValidate event.

                I would say this is driving me nuts, but i got there days ago.
                J.R.
                Epigate Software, LLC.

                [email protected]
                http://www.epigate.com
                sigpic

                Comment


                  #9
                  Re: Remain on current dialog record

                  For anyone with a dialog with a repeating section, can you test your dialog by editing a field in the repeating section and saving. Does anyone get an error, or does it save without any problems?
                  Monday morning presentation, but this is going to come out bad unless i can fix it. Appreciate any help.


                  error_dialog.gif
                  J.R.
                  Epigate Software, LLC.

                  [email protected]
                  http://www.epigate.com
                  sigpic

                  Comment


                    #10
                    Re: Remain on current dialog record

                    Thanks to Selwyn for figuring this out, I never would have. It seems the problem was due to having a hidden field in the repeating section that was the primary key. I come from VB/VBA background so having the primary key in a subform was no issue there. Since i didn't need those fields there, i removed those fields and everything works as it should. Thanks to Selwyn and everyone who helped. Hope this helps someone else from pulling their hair out.
                    J.R.
                    Epigate Software, LLC.

                    [email protected]
                    http://www.epigate.com
                    sigpic

                    Comment


                      #11
                      Re: Remain on current dialog record

                      I am getting the same error you were getting in March: "Record not found. After Executing SQL SELECT to refresh row in section"
                      Do I understand you correctly that the fix was to take out the controls that were bound to primary keys?

                      Comment


                        #12
                        Re: Remain on current dialog record

                        Removing that hidden field resolved the issue, but if i understood Selwyn correctly, they were going to fix it where that would no longer be a problem. I had the records unique ID in each of the repeating sections as a hidden field, but once i removed it, the problem was gone.
                        J.R.
                        Epigate Software, LLC.

                        [email protected]
                        http://www.epigate.com
                        sigpic

                        Comment

                        Working...
                        X