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



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

Application Upgrade Errors

  • Filter
  • Time
  • Show
Clear All
new posts

    Application Upgrade Errors

    We have an application which we periodically upgrade with a .zip file containing only the new applicaton files, not the data files. After the upgrade, we often experience several users who call us saying they are getting "object not found" or "script not found" errors (don't remember which). Typically, we then close the database, reopen it, and the error does not recur. This means the application becomes pretty stable over a period of time until our next upgrade, at which time, we again go through a new series of errors, typically solved by closing and reopening the database.

    Can anyone give me a suggestion about what is going on, and perhaps a way to prevent these errors from occurring?

    -- Dick James

    Re: Application Upgrade Errors

    Hi James,

    I know this wont help but it has been said many times before, "If it aint broke, dont fix it".

    If the application is running smoothly, what benefit will be gained by installing a new patch?

    One thing to check before running a new patch, make sure Alpha is not running.
    Keith Hubert
    Alpha Guild Member
    KHDB Management Systems
    Skype = keith.hubert

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


      Re: Application Upgrade Errors

      Its a good idea to incorporate a means for your users to do a full database compact after installing such upgrades. Amongst other things this will rebuild all the system indexes. (Here I would give a plug for Cal Locklins excellent index rebuild utility to be incorporated in your applications as this will rebuild index definitions as well as the index files) This should instantly lead to greater stability in your application.
      The downside to bear in mind is that any accidentally deleted records will be removed from the system during this process.
      If you are running shadowed the above processes need to be run directly on the master copy on the server with ALL other users logged out.

      Bob Whitaker


        Re: Application Upgrade Errors

        Dick, I'd like to emphasize Bob's last point. The upgrade of new application files should occur when none of your users have Alpha Five running. -- tom


          Re: Application Upgrade Errors

          We have an Update Version button on a form which executes several other scripts, but then executes the following:

          Current_Path = a5.Get_Path()
          Source_File = left(Current_Path,len(Current_path)-3)+" Backups\"
          The reason for the shortened path is that we keep each customer in a separate folder identified by a two letter code. For example:

          c:\Application Name\xx\...

          After this finishes, the application ends and must be restarted. We also have a compact & repair button on the application, which I thought would rebuild indexes.

          I will try to get an exact copy of the error messages we are seeing. Fortunately, they happen only occasionally, and they can evidently be eliminated by ending & then restarting the application.

          -- Dick James