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

parentform.commit() weird problem

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

  • #16
    Re: parentform.commit() weird problem

    Originally posted by Al Buchholz View Post
    What if you replace the close and reopen of the form found on the 'Add Another Address' button with this: (this uses your onactivate code insteadof doing all of the work of closeing and re-opening the same form. Which I'm assuming is to call your onactivate event.??)

    Code:
    topparent.Commit()
    'parentform.Close()
    '
    'form.view("mail_info")
    parentform.New_Record()
    parentform:record_entered.value=date() ' since this field is hidden on the form, you could also accomplish this with a field rule default value.
    Interesting this works for me. So what build of Alpha are you using and what operating system do you have?
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.

    Comment


    • #17
      Re: parentform.commit() weird problem

      Tried your suggested code but my problem remains!

      My OS is Windows 10. Alpha Five is build 3359. There was a later build but when I installed it some code would not work so I went back to the previous build. It has been some time ago so I don't remember what the problem was. Until now I have never had any problems. I am using Alpha Five 10 in compatability mode.

      Comment


      • #18
        Re: parentform.commit() weird problem

        Originally posted by Arlen View Post
        Tried your suggested code but my problem remains!

        My OS is Windows 10. Alpha Five is build 3359. There was a later build but when I installed it some code would not work so I went back to the previous build. It has been some time ago so I don't remember what the problem was. Until now I have never had any problems. I am using Alpha Five 10 in compatability mode.
        I run 4369 - 3712 on windows 7 compatibility on windows 10 and the code runs fine. That has been a very stable release.

        You may want to review the other code that gave you problems and fix it.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.

        Comment


        • #19
          Re: parentform.commit() weird problem

          My OS is Win10 and I opened the file in v11 without any incident or need to double click. Also after saving the new record, a simple topparent.new_record() worked fine without having to close and reopen the form.
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment


          • #20
            Re: parentform.commit() weird problem

            I was having a similar problem. I have a form with an embedded browse, on the form are buttons to enter records into the child table. I was using "commit()" to save the record. I would have to click on the button twice for the new record to be saved. I changed "commit()" to "enter_end()". The buttons now work with one click.

            Jeff C

            Comment


            • #21
              Re: parentform.commit() weird problem

              Originally posted by Jeff Carroza View Post
              I was having a similar problem. I have a form with an embedded browse, on the form are buttons to enter records into the child table. I was using "commit()" to save the record. I would have to click on the button twice for the new record to be saved. I changed "commit()" to "enter_end()". The buttons now work with one click.

              Jeff C
              Jeff

              Can you show a little more of your code and where it is located?
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.

              Comment


              • #22
                Re: parentform.commit() weird problem

                Each button has its own data for the field "action". Here is the code for one of the buttons:

                browse1.activate()
                :payments:tables:custrec.enter_begin(Honor_Field_Rules)
                :payments:tables:custrec.action = "17 PROPOSAL RET"
                :payments:tables:custrec.date = date()
                :payments:tables:custrec.enter_end()
                Parentform.resynch()

                When the button is pushed the script enters into the child table; "17 PROPOSAL RET" in the field "action" and the system date into the field date. The record is then saved. When I was using "commit()" instead of "enter_end" the button would enter the text and date but it wouldn't save. If I closed the form after pushing the button I would get a prompt do I want to save entry in progress. If I clicked on the button twice it would save the record.

                Jeff C

                Comment

                Working...
                X