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

tables are left open

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

    tables are left open

    Hello All,
    I noticed that after I close my form some tables are left open .I checked the object-explorer and no object is open .I close all tables , opened by "table.open"
    in my scripts and I have error handling routines in the scripts that change or enter tables. I make sure that dialogs windows are closed. But still tables are
    left open. What am I doing wrong or not doing. Dose it create a problems to have tables left open.

    Thank you
    Nick

    #2
    Re: tables are left open

    Nick,

    This would worry me. The tables supporting your form should close when the form closes. Can you repeat the issue on demand? If so, maybe its time to doublecheck everything again. Often it helps me when a different pair of eyes checks my work. So you might want to post a sample here, with instructions for us to follow your repeatable sequence. Maybe we'll notice something you're missing.

    Comment


      #3
      Re: tables are left open

      It worries me too when this happens. Two circumstances I can think of to get out of the way first.

      1. If you are developing and testing on the same load-up of Alpha (which is usual). Close down and restart. Go through the procedures only testing first and see if the problem repeats.
      The editor open linked to a form could be a cause.

      2. If you are opening any forms as dialog, read the docs on closing. Using normal form exit only hides the dialog form.

      Please correct me if I am wrong Tom.

      Comment


        #4
        Re: tables are left open

        Ray, that's solid advice. Simply closing the "window" of a form opened as "dialog" does not actually close the form in memory.

        Nick, after you close all forms the control panel menu has a useful option for you. Choose File, then Workspace Information. Any open tables will be flagged for you there.

        Comment


          #5
          Re: tables are left open

          I always close the dialog windows from the calling scrip . I test for files left open by running "?table.enum_open()" in the interactive window .I use
          "A5_forceclosetables" to close all table from interactive window the run each form that is opened from the main form and test them individually .I will
          try Rays suggestion .

          Thanks
          Nick

          Comment


            #6
            Re: tables are left open

            I can not figure this out .After I close my the form I check the object explorer and no object is open so there could not be a hidden form open.
            I went over my code many times and I know any "table.open " is closed by the end .Do I need to delete the pointers to open tables ,created using
            "table.get('Tbl')" .May be this is something common but people don't realize it when it happens .I was wondering if some of you guys could check and see
            if the same situation occurs in your work too . I am out of my wit's and depth again but this time there is no work around.

            I appreciate any help.
            Thanks
            Nick.

            Comment


              #7
              Re: tables are left open

              Hi Ray,
              If you are opening any forms as dialog, read the docs on closing.
              Could you please point me to the docs regarding this. I have the same problem.
              Regards
              Keith Hubert
              Alpha Guild Member
              London.
              KHDB Management Systems
              Skype = keith.hubert


              For your day-to-day Needs, you Need an Alpha Database!

              Comment


                #8
                Re: tables are left open

                Sample code I use Keith
                Form called a_form
                Opening
                Code:
                if is_object(":a_form")
                  :a_form.show()
                else
                  form.view("a_form","dialog")
                end if
                Closing
                Code:
                if is_object(":a_form")
                	:a_form.close()
                end if

                Comment


                  #9
                  Re: tables are left open

                  Ray,

                  Excuse me for being thick, is the :part of the form name?
                  Regards
                  Keith Hubert
                  Alpha Guild Member
                  London.
                  KHDB Management Systems
                  Skype = keith.hubert


                  For your day-to-day Needs, you Need an Alpha Database!

                  Comment


                    #10
                    Re: tables are left open

                    Originally posted by Keith Hubert View Post
                    Ray,

                    Excuse me for being thick, is the :part of the form name?
                    It's the syntax to be used with any form name

                    Comment


                      #11
                      Re: tables are left open

                      Thanks Ray ,Here is my code .I don't check for a open form because I do not plan to have one open.

                      details=:form.load("cust_order_detailes","dialog","center","center")
                      details.baseQueryRun(query.filter,query.order)
                      details.refresh_layout()
                      details.show()
                      details.close()

                      Is there a problem with code.
                      Thanks again
                      Nick
                      Last edited by Farzadalpa; 04-16-2013, 11:00 AM.

                      Comment


                        #12
                        Re: tables are left open

                        Originally posted by Keith Hubert View Post
                        Hi Ray,Could you please point me to the docs regarding this. I have the same problem.
                        It is not explicitly spelled out but this note in the form.view() section of the docs only applies to forms opened in dialog style.

                        Note : If you do not close the form at the end of your script, you will leave the underlying table(s) open.

                        Obviously the statement couldn't apply to all style choices of form.view() . Create a button on some form to open another form (action scripting). On the Options tab, Window Style leave the choice as normal and finish. Now view the xbasic of the action script element. Now change the Window style to dialog and view the xbasic.
                        There can be only one.

                        Comment


                          #13
                          Re: tables are left open

                          Originally posted by Farzadalpa View Post
                          Is there a problem with code.
                          Nick
                          Dunno, you tell us.

                          Comment


                            #14
                            Re: tables are left open

                            Your code is correct assuming that you have assigned values to query.filter and query.order.
                            There can be only one.

                            Comment


                              #15
                              Re: tables are left open

                              Originally posted by Keith Hubert View Post
                              Ray,

                              Excuse me for being thick, is the :part of the form name?
                              Originally posted by Ray in Capetown View Post
                              It's the syntax to be used with any form name
                              It is used to address a form, but it is not part of the form.load function

                              I would guess that running debug(1) through this code would show that the statement is syntactically incorrect...

                              This is from the help file....
                              Code:
                              This script loads the Customer form into memory. It then sets the form's filter and order properties and then shows the form.
                              
                              Form.load("customer")
                              
                              :customer:Tables:customer.filter_expression = "State_prov = 'MA' "
                              :customer:Tables:customer.order_expression = "Company"
                              :customer:Tables:customer.query()
                              :customer.show()
                              :customer.activate()
                               
                              
                              This script does the same as the previous script. It uses object pointers rather than the object name.
                              
                              dim frm as P
                              frm = Form.load("customer")
                              
                              frm:Tables:customer.filter_expression = "State_prov = 'MA' "
                              frm:Tables:customer.order_expression = "Company"
                              frm:Tables:customer.query()
                              frm.show()
                              frm.activate()
                               
                              
                              This script does the same as the above two scripts, but it uses the FORM.VIEWQUERIED() method (introduced in V5).
                              
                              filter = "State_prov = 'MA'"
                              order = "Company"
                              frm = Form.viewQueried("customer",filter,order)
                              I think 'Eagle Eye' Hubert found an issue to correct....
                              Al Buchholz
                              Bookwood Systems, LTD
                              Weekly QReportBuilder Webinars Thursday 1 pm CST

                              Occam's Razor - KISS
                              Normalize till it hurts - De-normalize till it works.
                              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                              When we triage a problem it is much easier to read sample systems than to read a mind.
                              "Make it as simple as possible, but not simpler."
                              Albert Einstein

                              http://www.iadn.com/images/media/iadn_member.png

                              Comment

                              Working...
                              X