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

Closing a series of forms

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

    Closing a series of forms

    I have 4 forms, each one opens the next in succession. Each form has a close button. I was wondering how one would close all the forms from a script in the last button using relative addressing.

    #2
    RE: Closing a series of forms

    Greg:

    One of my applications has several forms any combination of which may be open by the time the user wants to leave the application.

    Each form has an exit button which runs a logoff script. The script creates a pointer to each form and then
    if is_obj(formpointer)
    ..close this form
    end if

    and on to the next form.
    A5.close()

    This way you have only one instance of the code (the script) which works regardless of which forms are open.

    This keeps everything real simple and it hasn't created a problem in 2 years in a multiuser environment.

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: Closing a series of forms

      Bill, great idea.

      Question. How are the form pointers created in the first place? Do you create a pointer for each form as it's opened? If so, what scope do you use for the pointer to the new form?

      I see that if you didn't use is_obj(formpointer) but used is_obj(formname) you could also identify the open forms, and then close them. However, this would fail if two or more instances of the form were opened by the user in the same session. Alpha Five would give the second instance a different formname to keep them separate internally. The use of pointers neatly sidesteps this difficulty!

      -- tom

      Comment


        #4
        RE: Closing a series of forms

        Bill,
        Any chance you'd post your script?
        Ohlen

        Comment


          #5
          RE: Closing a series of forms

          I would like to see the script posted to Bill!

          Comment


            #6
            RE: Closing a series of forms

            Hello everyone:

            Here by popular demand is the code. You will see that it is rather unoriginal in that the error handler is "borrowed" from Steve Workings, the temp files delete code from Finian Lennon and the close function from the Xbasic documentation.

            The general idea is that since the logoff script creates its own session I do not have to know which form it is run from whereas were the same code attached to a form's button I would have to close that form last. At least I think I recall discovering this. (I wrote this a while ago.)

            Looking back I realize that whether in the application's ini script or from the main menu the application's forms are always loaded using the same pointers. A menu button can test for the existence of the pointer and merely show the form if it is already loaded. On the other hand, if the form has not been loaded, the button code can load and show it. The purpose of all this is to prevent duplicate open forms which would be big trouble for this application.

            The more complex forms are loaded and configured in the ini script. The others run from the main menu's buttons.

            I have put the script and the function in a single text file although they in use they are obviously two separate entities.

            Hope this is not too oblique.

            Bill
            Bill Hanigsberg

            Comment


              #7
              RE: Closing a series of forms

              This script closes all open forms and browses even multiple instances of the same form or browse.

              Allen

              Comment


                #8
                RE: Closing a series of forms

                Allen

                Thanks for posting the script. Nice job! Works great.

                Jerry

                Comment


                  #9
                  RE: Closing a series of forms

                  That's really nice. Much more than I needed in my specific circumstance but beautifully general and therefore more useful. Thanks for posting it.
                  Bill
                  Bill Hanigsberg

                  Comment


                    #10
                    RE: Closing a series of forms

                    Allan,

                    You should really consider posting this one in the code archive.

                    Bill
                    Bill Hanigsberg

                    Comment


                      #11
                      RE: Closing a series of forms

                      Allen:

                      Very, very nice!

                      Craig

                      Comment


                        #12
                        RE: Closing a series of forms

                        Allen & Bill,

                        Since everyone is sharing their version of closing all forms, I have posted my version of a global function in the Archive Section at

                        CloseAll script

                        It uses a similar searching for aliases as Allen's method, but keeps going until it stops finding them (with at least a minimum). It also handles the case where there are more than one object of the same name but different types (e.g. INVOICE form and INVOICE browse)

                        Bill - In the future, don't use spaces in your attached file name. It is difficult to retrieve because the board does not know it needs to put a %20 for the space to retrieve it. Also, I never have multiple copies opened of a form (unless I want it) because I always have code check for the layout being opened before opening it up. If you give access to the control panel, I guess you are out of luck.

                        Regards,

                        Ira J. Perlow
                        Computer Systems Design & Associates
                        [email protected]
                        Regards,

                        Ira J. Perlow
                        Computer Systems Design


                        CSDA A5 Products
                        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                        CSDA Barcode Functions

                        CSDA Code Utility
                        CSDA Screen Capture


                        Comment


                          #13
                          RE: Closing a series of forms

                          Thanks everyone, works like a charm!

                          Comment


                            #14
                            RE: Closing a series of forms

                            I guess I am lazy. I close my open forms by running a global script to close the database. An 'exit' form opens that has a custom menu with the close database item on it. sys_send_keys is used to close the database, then A5 is closed. The script is:

                            :a5.restore()
                            :a5.show()
                            :a5.maximize()
                            :controlpanel.hide()
                            :form.view("exit")
                            :exit.maximize()
                            sys_send_keys("{ALT-C}")
                            :A5.close()
                            end

                            Works very well here and doesn't care what forms are open, but i fail to take into account changes that aren't saved. Hasn't been a problem yet, but should probably include that.

                            Tom Lyon

                            Comment


                              #15
                              RE: Closing a series of forms

                              Hi Ira,

                              Thanks for telling me about spaces in attachments. I didn't know that.

                              As for allowing multiple instances of a form, I never allow that. The menu items check for an open instance before opening a form. Apologies if I mistakenly implied otherwise.

                              All the best,
                              Bill
                              Bill Hanigsberg

                              Comment

                              Working...
                              X