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

How to trap SQL errors in UX control during SAVE?

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

    How to trap SQL errors in UX control during SAVE?

    I am using a UX Control to write records to a database.
    Is there a way to trap certain SQL error codes when they occur ?
    For example how do I detect error code 1062 (which means Duplicate Entry on a unique index)

    I know of the "OnSQLExecuteError" server-side event in Grid component but I am looking for the equivalent in UX component.

    And please..... don't tell me to do a search for existing records before I do a save. I already know that method will prevent duplicates.
    I specifically want to know how to trap SQL errors if they should occur.

    #2
    Re: How to trap SQL errors in UX control during SAVE?

    I found a solution after examining some XBasic (behind the scenes) Code :


    In the UX component, afterDialogValidate event, place the following code after command ExecuteServerSideAction :

    ExecuteServerSideAction("Save Data::Save_Submitted_Data_to_Table_s_")

    'Trap for Duplicate Records:
    if rtc.fatalError = .t. then
    if atc("1062", rtc.errorText) > 1 then
    e.javascript = "{dialog.object}.showGlobalErrors('<Default>', 'Duplicate Entry found');"
    end if
    end if


    if rtc.flagRecordWasSaved then
    e.javascript = e.javascript + crlf() + "var ele = $('win_add_form');{dialog.object}.closeContainerWindow(ele);"
    end if


    ** I am using MySQL, so SQL error code 1062 represents Duplicate Entry

    Comment


      #3
      Re: How to trap SQL errors in UX control during SAVE?

      Thanks for sharing that. I will use this to trap the same error. Much nicer then the little red icon. Very clever.
      Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

      Comment


        #4
        Re: How to trap SQL errors in UX control during SAVE?

        Thanks for this, Robert! I just used it successfully on a UX component. Now I wish I was smart enough to make my error text pop up in a window...
        Carol King
        Developer of Custom Homebuilders' Solutions (CHS)
        http://www.CHSBuilderSoftware.com

        Comment


          #5
          Re: How to trap SQL errors in UX control during SAVE?

          Originally posted by kingcarol View Post
          Thanks for this, Robert! I just used it successfully on a UX component. Now I wish I was smart enough to make my error text pop up in a window...
          Wouldn't it be something like:
          Code:
          e.javascript = e.javascript + "alert('"+jsescape(rtc.errorText)+"');"
          ?

          Comment


            #6
            Re: How to trap SQL errors in UX control during SAVE?

            Smart, Jinx! The point of this thread is to not have that complex error wording, so taking your suggestion, I did something like this so a message would pop up AND the replaced text would also remain on screen..

            if rtc.fatalError = .t. then
            if atc("1062", rtc.errorText) > 1 then
            e.javascript = "{dialog.object}.showGlobalErrors('<Default>', 'Duplicate Entry found');"
            e.javascript = e.javascript + "alert('Duplicate Entry found');"
            end if
            end if
            Carol King
            Developer of Custom Homebuilders' Solutions (CHS)
            http://www.CHSBuilderSoftware.com

            Comment


              #7
              Re: How to trap SQL errors in UX control during SAVE?

              Please,


              How can I trap these MySql errors when using a list with detail?

              I would appreciate any tips.
              Tks,
              Cezar

              Comment


                #8
                Re: How to trap SQL errors in UX control during SAVE?

                Hi,
                Just got it.

                It is easy! Just open the Detail View pane and go to Server-side error message translate.

                Define a xBasic function to handle the error. Alpha writes the prototype for you.
                When there is a sql error, the error text can be found on e.errorMessage variable.

                Just check e.errorMessage for the error code you want, and change the e.errorMessage content to something understandable for the user.

                Tks,

                Comment

                Working...
                X