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

Disable ESC

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

  • Disable ESC

    I need to disable ESC when I zoom (in a set) to prevent the user from filling the zoom stack by not unzooming. This I can do but it needs to be conditional so ESC works in change or edit mode or in the memo editor and then is disabled again when the record is saved or memo is saved. I can get parts of this to work but the conditional part has me stumped. Any ideas?


    Russ

  • #2
    RE: Disable ESC

    I solved my own problem, just had to step back from it for a while. Used a variety of sys_trig_memo and sys_trig_rec triggers with onescape {}. Works fine.

    Comment


    • #3
      RE: Disable ESC

      Russ,

      You have a dia/monolog going here........ Can I butt in? I'd like to see one of your solutions. I've done this with complicated custom menu changes so that "unzoom' the was only menu [get-outa-here] option on a zoom-viewed form. This solution only 'hoped' that the user wouldn't use [ESC].Can you humor me?

      Ken

      Comment


      • #4
        RE: Disable ESC

        Ken
        I thought that I was able to correct this problem with $sys_trig_rec_save but I was wrong It seems to work some times but not always. What I have done now is when I go to a dbf or set where I don't want esc disabled I set onescape {{whatever}} to make esc do something else. When I am at the destination dbf esc is dasabled until I need it. On sub menu I set for "C" and "E" onescape {esc} to reenable esc. and on the same submenu for F10 run onescape {{whatever}}F10 to disable esc again when a record is saved from enter or change. The problem arises when a user presses esc from change or enter mode. on the submenu I have to set esc to run escape and I can't seem to disable it after the escape is completed. I tried
        "{ESC} {onescape{whatever}}" and "{esc}{onescape {set{sys_trig_rec_save,"escoff"}}" where escoff is a script to disable escape again but none of these seem to work. Escape is tough to trap (at least for me). I would live to hear ideas form anyone else on this.

        Russ

        Comment


        • #5
          RE: Disable ESC

          Hi Russ

          Have you thought of

          {ONKEYˇ"{esc}",ˇ{{If->this,{{esc},{{play my script}}}

          I use something like this for {F10} which checks for the form status i.e. "enter" or "change", and the values in certain fields before the record is saved.

          Hope this gives you an idea to work from.

          Good luck

          Robert

          Comment

          Working...
          X