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

Conditional object crashes A5

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

  • Conditional object crashes A5

    Here's a peculiar situation:

    I have a form with an embedded browse. The form uses a custom toolbar, one button of which closes the form (parentform.close()). I also have a conditional object on the form.

    If I set one of the conditions to be equal to a global variable, and go into the browse, and then click on the EXIT button, it crashes. If I open the form and DON'T go into the browse, it's OK. Also, if I set one of the conditions to be equal to a field value, it won't crash from the browse.

    Something that also happens, that might relate:

    I have an ONKEY script that closes the form when ESC is pressed. This will also crash the program as described above.

    It seems the program doesn't like the combination of evaluating a conditional object to a variable AND closing from the browse using ONKEY or the toolbar button.

    Any ideas?? All help greatly appreciated.

  • #2
    RE: Conditional object crashes A5

    Bill,

    Try moving the Exit button off the custom toolbar and place it directly on the form. Does that solve the problem?

    -- tom

    Comment


    • #3
      RE: Conditional object crashes A5

      Bill,
      No answer here but a workaround might be to put an object.activate() ( outside the browse ) just before the parentform.close.
      John

      Comment


      • #4
        RE: Conditional object crashes A5

        Hi Bill,

        What is the exact code of the exit button? In particular does it employ the "parentform" alias (or any other)?

        Bill
        Bill Hanigsberg

        Comment


        • #5
          RE: Conditional object crashes A5

          Thanks for the replies.

          Tom, a button on the form works fine. I suspect that is because clicking on the button returns focus to the form just before exiting.

          John, I tried

          parentform.activate()

          and

          :check_register.activate()

          just before parentform.close(). It still crashes.

          Bill, the code on the button (and in the ONKEY script) is:

          parentform.close()

          It's odd to me that this works fine if there is no conditional object (which would tend to argue against an alias problem), or if the cond object does NOT use a variable.

          Comment


          • #6
            RE: Conditional object crashes A5

            Bill,
            How about a button.push() that has the parentform.close() as the code.
            John

            Comment


            • #7
              RE: Conditional object crashes A5

              Bill,

              I would try
              this.close()'on the toolbar
              in place of
              parentform.close()
              because the toolbar has the same context as the form to which it is attached and parentform technically doesn't exist.

              Don't ask me how this issue might interact with the presence of a conditional object. That is far to inside for me.

              Bill
              Bill Hanigsberg

              Comment


              • #8
                RE: Conditional object crashes A5

                Bill W,

                Since the script works on the form but not in the custom toolbar I think maybe Alpha Five is confused about what the term 'parentform' refers to, when run from the toolbar. Is the toolbar part of the form? Is it a separate object altogether? I would think an absolute reference using the actual form name would work better.

                --tom

                Comment


                • #9
                  RE: Conditional object crashes A5

                  Since it's not confused if the conditional object doesn't have a variable reference and it also crashes in the onkey event, but a button on a form works okay, I still think that a button.activate() and a button.push() in the toolbar code has a pretty decent chance of working.
                  John

                  Comment


                  • #10
                    RE: Conditional object crashes A5

                    Bill, I tried

                    this.close()

                    I also tried (per Tom's suggestion)

                    :check_register.close()

                    but no difference...it still crashes.

                    I think I'll end up with replacing the conditional object with another way to do what I want.

                    Thanks to all of you for your suggestions.

                    Comment


                    • #11
                      RE: Conditional object crashes A5

                      John, that sounded like a GREAT idea. Unfortunately, it didn't work.

                      I also tried

                      sys_send_keys("{f6}")
                      parentform.close()

                      thinking that it would take me out of the browse before closing (since if I manually click on the form before clicking the button, it works).

                      No go.

                      Comment


                      • #12
                        RE: Conditional object crashes A5

                        Bill,
                        Just curious here.
                        1)On the toolbar code, if you just have a button.activate()with nothing else, does it activate the button and not crash???
                        2)If so, you might try putting nothing else in the toolbar code ( especially a parentform.close ) and put a parentform.close() on the onarrive event of the button.

                        John

                        Comment


                        • #13
                          RE: Conditional object crashes A5

                          Bill W,

                          Have you verified that the script will close the form when the conditional object is not present in the layout. If my guess is right your script will fail even when the conditional object is omitted altogether, provided it's run from the toolbar, instead of from a button on the form. I continue to think that the toolbar has a different idea about what the 'parentform' is, than do objects on the form itself.

                          -- tom

                          Comment


                          • #14
                            RE: Conditional object crashes A5

                            Tom,

                            I use parentform references frequently from both menus and toolbars without a problem. Normally, I might use a direct reference to a form name, but a number of toolbars and menus are used on more than one form. The only area I have found problems using parentform is from a form opened as a dialog. In that case, Alpha does get confused on exactly how to use the reference parentform.

                            Jerry

                            Comment


                            • #15
                              RE: Conditional object crashes A5

                              Jerry,

                              I use the "this" alias in toolbar code when I need to refer to the form to which the toolbar is attached.

                              Bill
                              Bill Hanigsberg

                              Comment

                              Working...
                              X