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

form.load() goes straight to show()

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

    form.load() goes straight to show()

    The following code has been working really well for half a year now but for some
    reason it has stopped behaving. I have an invoicing form that is based on a set

    SALESORDER=>SALES_ORD_DETAIL

    This is a tabbed form with a browse on each tab. SALESORDER on the first tab and
    SALES_ORD_DETAIL on the other. The idea is that the user would highlight the
    row on the browse he is interested in editing and then press an EDIT button
    There is an EDIT button on both tabs.

    The following code is found in the EDIT buttons. The only difference is the name
    of the form. My problem is with what happens when I try to open the form associated with the eesodet_pop form.

    I always get the previous record! It never pulls up the record the cursor is on
    when I press the EDIT button. In order to get to the desired record; I have to
    highlight the record I want on the browse; then I have to press the EDIT button
    to open the form, I would then close the form and press the EDIT button again.
    This is a real pain having to go in and out twice each time I have to edit a record.

    I have used the debugger to watch the vdetRec value. The correct value is actually
    getting into the variable. I is really frustrating to watch the program time and
    time again ignore the filter_expression. In fact, as I am going through the code step by step in the debugger, I find that the debugger stops at;

    f2 = :Form.load("eesodet_pop","Dialog")

    then it goes straight for ;

    f2.show()

    It doesn't bother going through the code in between! For some reason this happens only in the form that contains this EDIT button. This debugger behavior doesn't happen in any other form. The :form.load also fails to pick up the proper record.


    The following is the code in the EDIT button.

    vRec = Recno()
    vdetRec = alltrim(str(vrec))

    f2 = :Form.load("eesodet_pop","Dialog")

    f2:TABLES:sales_ord_detail.filter_expression = "between(recno(),"+vdetRec+","+vdetRec+")"

    f2:tables:sales_ord_detail.order_expression = ""
    f2:tables:sales_ord_detail.query()

    f2.show()

    Tags: None
    #2
    RE: form.load() goes straight to show()

    Is the eesodet_pop form already open when your Edit button is pushed ? Why aren't you testing to verify that's not open before loading another copy? Is it possible the dialog form is not being closed, and each push of the Edit button is loading another copy, with a different alias each time? Remember, closing dialog forms is handled differently than other forms. Ok?

    -- tom

    Comment

      #3
      RE: form.load() goes straight to show()

      Sorry Tom, I am afraid that I hit this problem before and Peter Greulich provided a simple solution. He simply put a f2.resynch() prior to the show() command and everything falls into place.

      Regarding your question, the dialog form is closed once within the form and once by the calling button. I have checked for any form remnants and there never is any. I have never made it a practice to verify the existance of a form but now that I have it in my library of routines, I hope that it will save many more hours of heartbreak.

      Thanks!

      Comment

        #4
        RE: form.load() goes straight to show()

        Great! I'm glad you got it going. Resynch after the query makes sense.

        The test for an open form is easy, is recommended.

        There are at least 2 ways to do it:

        p. 99

        p. 142

        both in the xbasic Ref. manual.

        Comment

          #5
          RE: form.load() goes straight to show()

          Tom, After testing for the existence of a form prior to opening a form is it not best practice to close the existing Form? I ask this because I feel that it is best to start with a clean slate. But then I have noticed situations in the past where I have found multiple instances of a particular form. The name of the form was followed by a numerical value, for example: eesales, eesales0, eesales1 etc.

          Would the isobject() command pick up on this?

          Comment

            #6
            RE: form.load() goes straight to show()

            Greg,

            My own practice is to work with the existing form, rather than closing and re-opening it. However, I'm always careful not to assume anything about the condition of the form, so I set its range, sort order, and mode before showing it. I think closing and reopening increases the load on the local network for no good purpose.

            -- tom

            Comment

              #7
              RE: form.load() goes straight to show()

              Thanks Tom.

              With regard to the debugger problem, have you ever encountered this skipping behavior?

              Comment

                #8
                RE: form.load() goes straight to show()

                Greg,

                No. I don't use the debugger a great deal. Do recall that it has both 'skip into' and 'skip over' icons that can be used to step through the script. If you chose the one which does not step through function calls, that might explain what you saw.

                -- tom

                Comment

                  #9
                  RE: form.load() goes straight to show()

                  I can't imagine not using the debugger, I'd be completely lost. I use it for everything so I am sure that I am not pressing the wrong icons. It is so weird that it does this.

                  Comment

                    #10
                    RE: form.load() goes straight to show()

                    Greg,

                    I find it often faster and easier to use the trace window. When I want to verify that a particular snippet is working correctly I write something to the trace window, that I can quickly check.

                    Ui_msg_box() is another way of doing the same sort of thing. You can use it to notify you of things that are going on, or of processes that have completed.

                    -- tom

                    Comment

                    Previous template Next
                    Working...
                    X