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


  • Filter
  • Time
  • Show
Clear All
new posts

  • Upgrade

    We have an excellent accounting program written in A5V1 and would like to upgrade this program to A5V4.5. There are numerous scripts in the original program that do not work in A4V4.5.

    How would one go about updating this program? Is there any way to track down the scripts that error?

  • #2
    RE: Upgrade

    Sure there's a way to track down the scripts that cause errors - run each script one at a time! (Aren't I helpful!!)

    I've found the most common cause to be the use of DB_RESET(). Unfortunately, I used this a lot with A5v1 (had to) but it is forbidden in A5v2 and later. When you make the changes, you will find that it is not always a simple substitution but may require some slightly different logic since you will now be opening another instance of a table rather than resetting the 'main' table.

    The new method actually has a number of advantages but it's annoying and time consuming if you have a lot of scripts that need to be modified. My preference is generally to convert the whole script to v4 methods while I'm at it because:
    (a) I don't know what V1 features won't work in the next versions,
    (b) the new scripts are easier to read/troubleshoot,
    (c) there are often find better ways to do things in v4,
    (d) I think I sometimes had trouble with mixing old A5v1 methods with A5v4 in the same script(??),
    (e) This is a minor issue: I can re-save them in the database which is the default location in v4. (In v1 they are saved with the individual tables.), and
    (f) I often had more than one script with the same name in V1 because the scripts were saved with the tables/sets and it didn't matter if names were the same. In v4 it does matter. If you don't pay attention, you may run a script belonging to another table. (Assuming you named your scripts - which many people didn't. Of course, this brings up another issue... If you didn't name your scripts then you now have a bunch of really logical names like "{SCP083487457}" to deal with - fun, fun, fun!)


    • #3
      RE: Upgrade

      Cal, thanks so much for your reply. Looks like I have my work cut out for me. It would seem a shame to loose all the effort that was put into the original program.


      • #4
        RE: Upgrade

        James, One major scripting change I had to make was in OnFetch and New Record events. In 4.5 they changed the code so that an ENTER record causes an OnFetch operation to occur - because of this change, you may need to re-arrange some scripting as some events may fire out of turn. This ifno was supplied to my by Cian from A5.


        • #5
          RE: Upgrade

          Thanks for that little "tidbit". I haven't upgraded to v 4.5 yet, but since I use a number of OnFetch event scripts, I can see that the change will give me some interesting headaches. Quess it is time to rethink some actions.