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

Zoom to Record Error Message Change

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

    Zoom to Record Error Message Change

    Is there any way to change the error message "You can only Zoom...." to somethng like, "Click on a row to open detailed form."? I can't imagine someone understanding Zoom and focus who isn't familiar with Alpha, let alone know what "embedded" means. This seems to be an internal error message.

    Thanks

    Pete
    "Ollie, remember how dumb I used to be? Well, I'm much better now."

    Pete

    #2
    Am I just asking a dumb question? I tried error handling with no success. I still don't know how to fix this. Any help would be appreciated. I promise, I will get better.

    Thanks,
    Pete
    "Ollie, remember how dumb I used to be? Well, I'm much better now."

    Pete

    Comment


      #3
      Pete, as a general rule the error messages generated by Alpha are not user configurable. However, you can often create custom versions of the supplied functionality. In your custom scripts you can define your own messages. In this case for example perhaps you'd be happier with a button you create that runs the Zoom-to-record action script. Once this is saved you could convert the action script to xbasic and tweak the user messages, I would suppose (easy for me to say, since I've never done it!).

      -- tom

      Comment


        #4
        Tom:
        Thanks for replying. I do have my own button and then did a Zoom to Record Expression through the genie. Since I am still in my rookie campaign, I tried to follow the rules for doing an error handling (I figured out just what you said, that the error message is for me and not for the end user). My lack of ability to understand x-basic is the drawback to writing proper code to customize my own message. I will continue looking to see where I can learn this. My one frustration with the documentation is that the examples are not yet clear to me. I have gone through this before in another product using different code language, so I know it will just take some time and lots of trial and error.

        Thanks again. It's really nice that you are willing to spend a lot of your time answering questions for so many posters.

        Pete
        "Ollie, remember how dumb I used to be? Well, I'm much better now."

        Pete

        Comment


          #5
          Hi Pete,

          As an 'easy' fix, why don't you just make your zoom button larger, align it across the top of your embedded browse and on the button put something like: "HiLite row and then press here to zoom to record detail." If the user presses the button without highlighting a row it will be obvious to them what the Alpha error message means.

          My limited experience is that some of the Alpha error messages can be found in the xbasic script and therefore modified easily, while others are at a 'deeper' level.

          Good Luck!

          Bob Arbuthnot

          Comment


            #6
            Here is what I tried in following directions to catching errors.
            Code:
            on error goto error_handler
            end
            'put Xbasic code here
            'Zoom to dialog form 'AthleticInfo'.
            [B]dim Shared varP_ZoomForm as P
            varP_ZoomForm = topparent.zoom_to_record("AthleticInfo","dialog")[/B]
            
            error_handler:
            
                err = error_code_get()
            
                msg = error_text_get(err)
            
                ui_msg_box("Error", "You must first highlight an athlete before selecting this button.")
            
            end
            The bold is the x-basic code for Zoom to Record. End result is that nothing happens, including not going to Zoom record when a row is highlighted.
            "Ollie, remember how dumb I used to be? Well, I'm much better now."

            Pete

            Comment


              #7
              Pete, I was imagining a script that began by verifying that the browse object had focus, displaying a custom ui_msg_box() to the user if it did not...

              -- tom

              Comment


                #8
                Tom:
                I understand your point. As expressed earlier, my xbasic skills are zero.

                I have a browse and to Zoom to Record, I must first click on a row. I will now try and learn how to verify that the focus is or is not on a row.
                Your suggestion is cleaner and easier than handling an error message (I would prefer to stay away from that). So, your point is well taken. Thank you again.

                Wish me luck....:)

                Pete
                "Ollie, remember how dumb I used to be? Well, I'm much better now."

                Pete

                Comment


                  #9
                  <object>.active_prev() example

                  Pete,

                  Here's an example to get you going. Unzip the attachment to an empty folder. The button on Form1 will test whether the browse object had focus immediately prior to the button push.

                  -- tom

                  Comment


                    #10
                    Tom:
                    Your solution is very simple and direct. I really appreciate the private lesson!
                    Thanks, again.

                    Pete
                    "Ollie, remember how dumb I used to be? Well, I'm much better now."

                    Pete

                    Comment

                    Working...
                    X