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

Table Resturcturing Error - table being used

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

  • Table Resturcturing Error - table being used

    We have been an Alpha user since 1995 with hundreds of tables and sets. Within the last 3 weeks we began encountering a odd error. When restructuring a table, ie - adding a new field or changing a field length, we get the following error AFTER we have made the table change and have selected Save. "The process cannot access the file because it is being used by another process."

    We know for certain that no other activity is using the table in question, or the entire Alpha system, for that matter. We have tried copying out the database to other systems and get the same error. We do not get this all of the time, but we have noticed it is occurring more frequently. We have also noticed that even though we get the 'being used' error when trying to restructure a table, we can still rebuild it's indexes or Pack the table ... activities which we should not be able to do if the table was truly 'being used'.

    We have been playing with this for days, without a clue as to why we are seeing the 'being used' message. Does anyone have any thoughts?

  • #2
    I am not, nor have I ever had an issue like the one you describe. I'm thinking the issue is yours, alone.

    Have you changed the version of AA you were using anytime recently? If not, that takes AA out of the scope of the cause.

    You may have scripts opening tables, and the pointer is not being closed at script completion.

    There may be errors in scripts where the script does not complete, so the table is not closed.

    The server where the data is being stored may be scanning with an AV software, or backing up, or other activity that flags the file set associated with the table as in use.

    The next time it happens, go to the file server and see who or what has the file open. If Windows, then go to Control Panel - Administrative Tools - Computer Management - Shared Folders - Open Files.

    A bit of detective work from there might help you close in on the issue.

    Just for the sake of the try, have you done a backup and then a database compact?

    Is it possible a user is closing the AA app on his computer, and it's hanging - visible only in task manager?

    Or are you using A5.HIDE()?

    I know these are long shots, but it's where I'd start.

    Comment


    • #3
      What backup system are you using for those machines?

      Is it possible that the interference is coming from that?
      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.

      Comment


      • #4
        We use a Datto Backup and Recovery Appliance. It has been running for several months now without incidence. Still, an interesting thought, Al. We also began using Alpha Release 6699 just prior to these table restructure issues. Coincidence? Probably .....

        We are now testing this problem with prior Releases of Alpha on isolated copies of our Data Base; machines with nothing else running on them.

        Thank you Al and Craig for your thoughts ...

        Comment


        • #5
          Originally posted by jeffemery View Post
          We use a Datto Backup and Recovery Appliance. It has been running for several months now without incidence. Still, an interesting thought, Al. We also began using Alpha Release 6699 just prior to these table restructure issues. Coincidence? Probably .....

          We are now testing this problem with prior Releases of Alpha on isolated copies of our Data Base; machines with nothing else running on them.

          Thank you Al and Craig for your thoughts ...
          Did you try to restructure prior to upgrading Alpha?

          So you have 2 tests to run.

          1. is to roll back to the previous version of Alpha.
          If you have a test machine that is where to do that.

          2. stop the backup system or do it on a test system that isn't being backed up on a directory that isn't part of the backup. (probably better)

          You want to do those steps separately so you know what part is the issue.

          I'd a third test also.

          Duplicate (data, field rules, all options - ie a complete duplication) the table to a new name - shorter than 10 characters and try to restructure that table

          Duplicating is a magic pill that solves a lot of internal problems.
          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.

          Comment

          Working...
          X