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

Dialog won't commit changes except when in debug

  • Filter
  • Time
  • Show
Clear All
new posts

  • Dialog won't commit changes except when in debug

    I have a complex dialog (2) in V. 11 which will not commit the changed record unless I run it through the working preview in debug mode.
    I know this is so because of two issues: the backend SQL table won't update, and the Submit button won't go dim
    When I run it through live preview, it won't commit the change, and when I remove the debug, it won't commit the change.
    When I run it through the working preview in the debug(1) mode, it does commit the change to the SQL table, and the Submit button goes dim.
    I have tried adding an xbasic_wait_for_idle() before and after the a5DialogHelper_SaveData(tmpl, e, rtc, flagUseTransactions, opx), but to no avail.

    Any thoughts?
    Jay Talbott
    Lexington, KY

  • #2
    Re: Dialog won't commit changes except when in debug

    I've had to run my dialog through FireBug on occasion to figure out what was failing. Have you looked at it in FireBug?
    Alpha Anywhere latest pre-release


    • #3
      Re: Dialog won't commit changes except when in debug

      No, Sarah, I have not.
      I will do that and let you know what is happening.
      Jay Talbott
      Lexington, KY


      • #4
        Re: Dialog won't commit changes except when in debug

        This is what Firebug shows. Does anything look out of place?

        V.R1.DATE_CREATED 05/01/2012
        V.R1.DIVISION 80
        V.R1.INVOICE_NUMBER 296060
        V.R1.PO_NUMBER 259894
        V.R1.SHIPMENT_NUMBER IT 041007 0210 0
        V.R1.TOTAL_CHARGE_AMOUNT 282.5
        V.R1.UNITS 168
        V.R1.VENDOR_NUMBER 378471
        V.R1.XFER_FROM jay
        V.R1.XFER_TO jat
        _XbasicFunction system:submitDialog
        __Ajax true
        __FormAction GenericAjaxCallback
        __FormID undefined
        __submitType none
        _currentRow 1
        _part G
        _state.__dialogGuid 3d5c6113-01e3-4c74-9931-2e345439de6c
        _state.__dtfmt MM/dd/yyyy
        _state.__os c4t3THFpLW5VL2grcVxxLjCVbGRli0sjRzYrNW1WdT5pKzclMkZYSTUtaCl9SZaLekGW
        old.V.R1.CURRENCY USD
        old.V.R1.DATE_CREATED 05/01/2012
        Jay Talbott
        Lexington, KY


        • #5
          Re: Dialog won't commit changes except when in debug


          One of the things I've started doing is put error handling in the server-side events. I've had the sort of behavior your describing and been able to track down errors (bugs) that way.

          Something like:
          on error goto error_out

          ...your code...

          e.javascript = "alert('afterDialogValidate Error: " + js_escape(error_text_get(error_code_get())) + "');"
          - Dan Hooley
          - Custom Desktop or Web database development -


          • #6
            Re: Dialog won't commit changes except when in debug

            That was an excellent suggestion.
            I ran it, and here is what I got:
            afterDialogValidate Error: a5DialogHelper_daveData(tmpl,e,rtc,flagUseTransactions,opx): Too many parameters

            Searching the message board does not give me a good answer. Any thoughts?

            Also, even thought I have the "Display debugging info" box checked, I see no SQL statement displayed. Any thoughts?
            Thanks again.
            Last edited by Jay Talbott; 05-02-2012, 10:01 AM.
            Jay Talbott
            Lexington, KY


            • #7
              Re: Dialog won't commit changes except when in debug

              Anything related to 'a5DialogHelper' sounds like a bug. You might check your release version and try one previous or next. If you can create a test case, send it as a bug.
              - Dan Hooley
              - Custom Desktop or Web database development -


              • #8
                Re: Dialog won't commit changes except when in debug


                Don't know if this will help, but I have seen this same behavior in a dialog I created. Submit would not perform the update, but when I stepped with debugger, the change was committed. And using live preview did not show any kind of error.

                In my case, it turned out there was some additional xbasic code (I think I was trying to do an xbasic validation) that had a syntax error in it. You may want to look for something else that is attempting to execute that is failing.