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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Do you can capture error and customized message display?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Do you can capture error and customized message display?

    I need capture error from mi application and display a dialog box,what is command for active is condition.

    Thank�s
    Tags: None
    #2
    Re: Do you can capture error and customized message display?

    Not sure if this is what you want, but I use the following for error control...

    On Error Goto Proc_Err

    <code>

    Proc_Exit:
    end

    Proc_Err:
    err = error_code_get()
    msg = error_text_get(err)
    ui_msg_box("Error Title", "Error # : " + err + " : " + msg)
    resume Proc_Exit


    If you want to check for a specific error have a look in the help file - "Handling Errors" - and you'll find an error number list.

    Comment

      #3
      Re: Do you can capture error and customized message display?

      Originally posted by Davidk View Post
      Not sure if this is what you want, but I use the following for error control...

      On Error Goto Proc_Err

      <code>

      Proc_Exit:
      end

      Proc_Err:
      err = error_code_get()
      msg = error_text_get(err)
      ui_msg_box("Error Title", "Error # : " + err + " : " + msg)
      resume Proc_Exit


      If you want to check for a specific error have a look in the help file - "Handling Errors" - and you'll find an error number list.
      " NOT WORK"

      Comment

        #4
        Re: Do you can capture error and customized message display?

        Pretty sure it does... the <code> part is where your xbasic code goes for whatever you're doing. I copied this straight out of one of my routines. When an error occurs... it gets trapped.

        Comment

          #5
          Re: Do you can capture error and customized message display?

          " NOT WORK"
          Fernando,

          I am certain that your grasp of English is better than mine of your native language.

          In any event, " NOT WORK" doesn't help us determine what your problem might be nor does it lead anyone, myself at least, want to lend further aid.

          How did you implement the suggested code?

          I need capture error from mi application and display a dialog box,what is command for active is condition.
          There is no "command" that will display a dialog, in all situations, that will inform the user of the current problem. There are too many possibilities for that to be possible.

          More information is always better than less.

          "capture error" - what error, type of error, (show us an example)? Elaborate more on what you are seeing,
          There can be only one.

          Comment

            #6
            Re: Do you can capture error and customized message display?

            Originally posted by Stan Mathews View Post
            Fernando,

            I am certain that your grasp of English is better than mine of your native language.

            In any event, " NOT WORK" doesn't help us determine what your problem might be nor does it lead anyone, myself at least, want to lend further aid.

            How did you implement the suggested code?



            There is no "command" that will display a dialog, in all situations, that will inform the user of the current problem. There are too many possibilities for that to be possible.

            More information is always better than less.

            "capture error" - what error, type of error, (show us an example)? Elaborate more on what you are seeing,
            Excuse, my english is poor, I`m old user Filemaker, into Filemaker it exists instruccion global CAPTURE ERROR and other for handler ERROR XXX into script,in alpha five I test different command in Script, and not work

            Comment

              #7
              Re: Do you can capture error and customized message display?

              My script convert in Xbasic is:

              'Open a Form or Browse layout, displaying all, or selected records in the layout.
              query.filter = "(Nombre = Var->vUSuario ) .and. (Nombre = Var->vClave )"
              query.order = "recno()"
              'replace variables in the filter with their actual values
              query.filter = convert_expression(query.filter,"V")


              'Open the layout_type showing just the records that satisfy the filter
              DIM Global varP_CLIENTES as P
              DIM layout_name as c
              layout_name = "CLIENTES"


              dim tempP as p
              on error goto error_handler

              'Get pointer to existing window. In case layout_name is qualified with a dictionary name, extract up to first @. In case formname has spaces, normalize it
              tempP=obj(":"+object_name_normalize(word(layout_name,1,"@")))
              'Test if pointer is valid
              if is_object(tempP) then
              'Test if pointer refers to a form or browse
              if tempP.class() = "form" .or. tempP.class() = "browse" then
              dim flagIsBaseFilter as l
              flagIsBaseQuery = .t.


              if flagIsBaseFilter then
              'Apply the query to the form or browse as the Base query. (this means that
              'the user cannot turn the query off, only add to the query)
              tempP.BaseQueryRun(query.filter,query.order)
              else
              tempP.QueryRun(query.filter,query.order)

              end if

              'then activate the already open window
              tempP.activate()
              else
              'Window is not already open, so open it
              varP_CLIENTES = :Browse.viewqueried(layout_name,query.filter, query.order )

              end if
              else
              varP_CLIENTES = :Browse.viewqueried(layout_name,query.filter, query.order )

              end if

              end

              error_handler:

              err = error_code_get()

              msg = error_text_get(err)

              ui_msg_box("Se genero un error", msg)

              end

              Comment

              Previous template Next
              Working...
              X