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.object}.submit() -- How to check for errors????

  • Filter
  • Time
  • Show
Clear All
new posts

  • {dialog.object}.submit() -- How to check for errors????

    On a dialog, I have the submit button. It executes in-line javascript, with the following line: {dialog.object}.submit()

    How do I check for an error in the submit???

    Right now, it is via action scripts, and the next line is a message box that says SAVED, but that isn't always accurate.

    How do I write error checking into the javascript function?


  • #2
    Re: {dialog.object}.submit() -- How to check for errors????

    Check afterDialogValidate() server side event



    • #3
      Re: {dialog.object}.submit() -- How to check for errors????

      Ok, checked it... and that's where I tell it to save the data.. but how do I check for errors? I can't find any documentation about error handling, or examples of such.... sorry for such a silly question, but they give great examples in the event, but nothing about error reporting...

      I want to display an alert message that says record saved successfully, or that an error, as well as what the error is (not referring to validation error, but errors like can't write to database or something like that) that occurred.

      Any help?



      • #4
        Re: {dialog.object}.submit() -- How to check for errors????

        First, it's not a silly question, in the contrary, that's our main bread and butter, saving stuff to dB's that is...;-)
        As for your issue, you should do all that checking and saving in the afterDialogValidate. You create a sql::connection object, do your stuff, then check callResult.Text for errors in the SQL.
        From here: http://www.downloads.alphasoftware.c...SQLTables.html :
        flag ="::Name::AlphasportsXbasic")
        dim sqlCommand as c
        sqlCommand = "Select * from customer"
        flag = cn.execute(sqlCommand)
        = .T.

        Checking for errors - CallResult.Text
        You can always see if a SQL command executed successfully by checking the connection object's callResult property

        = "Success"

        'Now, make an intentional error - there is no table called MyCustomers
        dim sqlCommand as c
        sqlCommand = "Select * from mycustomer"
        flag = cn.execute(sqlCommand)
        = .f.
        = Database API specific error

        Your database has returned the following error code and description to Alpha Five.
        Consult your database documentation for further information.

        208 - '[Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'mycustomers'.
        SQL State is: 42S02'


        • #5
          Re: {dialog.object}.submit() -- How to check for errors????

          Thanks for the indepth reply!!

          What if I'm using the ExecuteServerSideAction(Save Data::savedata)?

          I'm not manually writing out the SQL .. I did the insert Action Scripting.

          Thank you again!


          • #6
            Re: {dialog.object}.submit() -- How to check for errors????

            You should spend some time with the Alpha videos D8... an excellent series of videos that covers data validation.


            • #7
              Re: {dialog.object}.submit() -- How to check for errors????

              Thanks David, I've gone through them numerous times.. and I just went through them again, thinking maybe I missed something, but I'm not referring to data validation. I'm trying to determine how I can tell with certainty that when my AfterDialogValidate is called, when I issue the command "ExecuteServerSideAction(Save Data::savedata)" if an error occurs or not... and if so, how I let the user know what the error was.

              Or does ExecuteServerSideAction handle its own errors and display them (but then, how would I know if I can say "record saved successfully") ?

              Thank you.


              • #8
                Re: {dialog.object}.submit() -- How to check for errors????

                Hey Chris,

                Once the dialogValidate happens - which is you checking your data before submission - and there are no errors, then the afterDialogValidate runs and submits data. If there are any server errors then those will be caught by the ExecuteServerSideAction code and displayed. To see this code place your cursor on your ExecuteServerSideAction call and then click the Action Javascript button and then choose View XBasic. In there you'll see the error trapping code...

                if rtc.fatalError = .t. then 
                	'must set this flag to prevent the Dialog from clearing the error messages.
                	e.showGlobalError = .t.
                	dim errorText as c 
                	errorText = rtc.errorText
                	'errorText = stritran(errorText,crlf(),"<br>")
                	jsShowErrors = "$svs('"+tmpl.alias+".GLOBALERRORS','"+js_escape(errorText)+"'); " + crlf()+\
                	"$('"+tmpl.alias+".GLOBALERRORS').style.display = '';"
                	rtc.javascript.refreshAllControls = ""
                	rtc.javascript.setPrimaryKeyinStateObject = ""
                	rtc.javascript.prepareDialog = ""
                	jsToFireAfterSaveEvent = ""
                	jsEnterNewRecord = ""
                end if
                E.g. I start my dialog... it's blank, and I enter a record ID that already exists and and some other field value and submit. I then get a huge red box at the top of the dialog telling me there's been an error and what it is... a duplicate ID.

                If you'd like to show more, as you say like a "Sucessfully saved" message then you can do some checking as well - in the same manner. After your call to save the data put something like this...

                if rtc.fatalError = .f. then 
                	e.showGlobalError = .t.
                	dim errorText as c 
                	errorText = "Record successfully saved."
                	e.javascript = "$svs('"+tmpl.alias+".GLOBALERRORS','"+js_escape(errorText)+"'); " + crlf()+\
                	"$('"+tmpl.alias+".GLOBALERRORS').style.display = 'block';"	
                end if
                Further, you can change the "GLOBALERRORS" div style... change it to green, etc... 'cause it's red by default. Something like...

                	"$('"+tmpl.alias+".GLOBALERRORS').style.display = 'block';" + crlf()+\
                        "$('"+tmpl.alias+".GLOBALERRORS').style.color = 'green';" + crlf()+\
                	"$('"+tmpl.alias+".GLOBALERRORS').style.border = '1px solid green';"
                Last edited by Davidk; 05-31-2012, 01:51 PM.


                • #9
                  Re: {dialog.object}.submit() -- How to check for errors????

                  Ahhh ok, got it. Awesome, thank you David!!!! As always, you all rock!