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

"Could not open table" error

  • Filter
  • Time
  • Show
Clear All
new posts

  • "Could not open table" error

    When I try to pack one of my tables after deleting records I get the error: "Could not open table"

    I've confirmed that no forms are open and have restarted... suggestions?
    Kim Dickerman

  • #2
    Re: "Could not open table" error

    sounds like a corrupt table. Create a new table and append the data from the old table and give it a try.


    • #3
      Re: "Could not open table" error

      Kim, while Robert may be correct a table may be open even though all forms have been closed. A less drastic approach would be to approach the issue in steps.

      a) run a5_forceclosetables() from the interactive window. Try packing, if fails go to step b
      b) close and re-open the database. Try packing. If fails go to step c
      c) close Alpha Five, re-start, then re-open database. Try packing. If fails go to step d
      d) reboot your machine, start alpha five, re-open the database, try packing. If fails go to step e
      e) move the data to a new table, per Robert's suggestion

      If this problem occurs regularly then you should spend some time trying to figure out why it's happening. A common cause is failing to actually close a form that's been opened as DIALOG. The system menu ('X') and form close action scripts can't properly close these types of forms. As explained in the helps the script that opens these forms must close them.


      • #4
        Re: "Could not open table" error

        Thanks Robert and Tom,
        On your suggestion about using a5_forceclosetables(), to execute, (remember that I am still not even smart enough to be considered half a moron!)

        From the control panel, with all windows closed, I open the interactive window and insert a5_forceclosetables() and by pressing enter it runs? I don' t have to direct it to a form name or anything else?

        Your comment, "As explained in the helps the script that opens these forms must close them. "

        I've used the action scripting method to define the OnPush event for the button that is used to call this form and sort by matching record... Is this the script that is responsible for closing it? I've viewed that code and there is no :formname.close at the end of the code, only end if.

        Lastly, if the table is corrupt and I replace it, I will then be required to redefine the set, reassign the form, and redefine all fields/browses on the form - correct?
        Kim Dickerman


        • #5
          Re: "Could not open table" error

          insert a5_forceclosetables() and by pressing enter it runs? I don' t have to direct it to a form name or anything else?
          Correct. a5_forceclosetables() forces the closure of all tables. No parameters needed.

          Lastly, if the table is corrupt and I replace it, I will then be required to redefine the set, reassign the form, and redefine all fields/browses on the form - correct?
          If you duplicate the table and choose copy the data dictionalries, or copy the data to another table and copy the layouts to the new table, you need only remove the old table from the set definition and replace it with the new table.
          There can be only one.


          • #6
            Re: "Could not open table" error

            Thanks for the confirmation... Looks like I will be replacing a table!
            Kim Dickerman


            • #7
              Re: "Could not open table" error

              Make sure that you take Stan's advice about duplicating the table/set to a new name and see if the problem persists in the new table/set.

              Sometimes that will clear up issues...
              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.


              • #8
                Re: "Could not open table" error

                You also didn't indicate whether or not you are working on a network. If anyone else had the table open, that would also cause the problem.

                The following applies to any system - 1 computer or networked computers....

                NOTE: Just because you can't see the table open on a machine - or even Alpha open on a machine - doesn't mean it isn't open. The only real way to find out if all copies of Alpha are closed is to open the Task Manager and go to the Processes tab. (The Applications tab is NOT adequate for this check.) If there is an Alpha5.exe process running, then A5 is open. There may have been some form of crash/error that is causing it to remain open even though it can't be seen anywhere on the desktop or in the Applications tab of the Task Manager. If there are no copies of A5 open on the desktop, highlight Alpha5.exe and click the End Process button to kill it.

                Of course, shutting down all computers - including the server - will accomplish the same thing.

                SERVER NOTE: I've seen situations where every workstation was shut down but not the server and, even though there were no Alpha5.exe processes running on the server, something "recreated" the link to a table when the workstation was restarted. Unless you have a network expert who knows how to "break" such links (and don't call me, I have no idea how to do it), the best bet seems to be to shut down every workstation AND the server at the same time, restart the server first, THEN restart the workstation(s).


                • #9
                  Re: "Could not open table" error

                  Great feedback, I am currently a single user but will be deploying later. Nothing is showing up in the processes tab.
                  Kim Dickerman