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 the 'last' table.

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

    Closing the 'last' table.

    in order to compact the database, all tables must be closed.

    i almost always have one table that won't close. the only reliable way i've found is to close alpha 5 (not just the database) and restart it without the startup table then compact the database....

    even when i start the database without the startup table if i run some scripts and open some forms i end up (not always, but usually) with a table that can't be closed...

    alpha 4 was never like this.............

    #2
    Re: Closing the 'last' table.

    Jack, have you tried to determine why tables are being left open? Here are two commonplace explanations:

    a) during development you run scripts that open tables and then crash, leaving the tables open; or

    b) you open forms as "dialogs" and don't take the necessary additional steps to release them from memory after they close.

    Understanding why your tables are still open will help you get them closed properly.

    If you use a startup form as a sort of menu for the application, and leave it open throughout a session, you should be basing the startup form on a dummy table, which never has to be compacted cause it has no meaningful data in it.

    Comment


      #3
      Re: Closing the 'last' table.

      Originally posted by Tom Cone Jr View Post
      Jack, have you tried to determine why tables are being left open? Here are two commonplace explanations:

      a) during development you run scripts that open tables and then crash, leaving the tables open; or
      this most certainly does happen - it's not alpha 4...
      i have tried to close them even using various combinations of these:
      ?table.enum_open()
      ?table.enum_session_open()
      ToClose=table.get("**fill in the blank**")
      ?ToClose.close()
      table.reset("**fill in the blank**")
      a=table.current()
      ?a.name_get()
      a.close()

      the real reason for my whine is to see if there's a command or process that i'm missing... my memory is failing so i can't remember the entire wickipedia or help file like i could (and still can) with alpha 4.



      [QUOTE=b) you open forms as "dialogs" and don't take the necessary additional steps to release them from memory after they close.[/QUOTE]

      i've considered 'form as as dialogs', but haven't ventured that far yet...

      [QUOTE=Understanding why your tables are still open will help you get them closed properly.[/QUOTE]

      so, given either of those 2 cases, what are the two 'solutions'?

      [QUOTE=If you use a startup form as a sort of menu for the application, and leave it open throughout a session, you should be basing the startup form on a dummy table, which never has to be compacted cause it has no meaningful data in it.[/QUOTE]

      so you just skip it every time you compact??

      Comment


        #4
        Re: Closing the 'last' table.

        the real reason for my whine is to see if there's a command or process that i'm missing
        a5_forceclosetables()

        so you just skip it every time you compact??
        No, you compact from the controlpanel when all tables are closed.
        There can be only one.

        Comment


          #5
          Re: Closing the 'last' table.

          When you try to compact your application you are getting the name of the open table, which narrows the possible causes.
          This problem will not occur due to opening and closing plain forms and browses so it must be some script that is causing the problem.
          Whenever you table.open you must close() that table and most times this has been the cause when I have had the problem. If this fails to identify the problem note that some "operations" leave tables open. If so convert them to xbasic and modify the script to close the necessary tables(s).
          As Stan has stated, a5_forceclosetables() will close open tables but this should not be used as the solution - you must find why the table is left open and fix that problem.

          Comment

          Working...
          X