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

v.11 Desktop Anomalies & bug list (legitimate contributions welcome from all)

  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Re: v.11 Desktop Anomalies & bug list (legitimate contributions welcome from all)

    If this isn't a bug, it certainly "compromises" the reliability & usefulness of the backup/zip routines built into a5!
    (They don't backup these dropped tables.)
    v.11 (Build 3211 Addins: 4072) ~ 01/24/2013
    History: Unknown.

    If you drop a table (accidentally), any set relying on that table can't tell the difference. (And consequently, all layouts based on that set will continue to run even though a table in the set has been dropped and is presumably missing. ~ It definitely doesn't show up in the CP! In most instances, (when you drop tables) any reference to any layout object (aka form report etc.) that was "tied" to the dropped table will cause an error when running the db. (when code references the dropped layout object) This is not the case with sets.

    Here's the real problem/threat: Sending, backing up & zipping the database that has a table that was dropped inadvertently creates a broken copy with a missing table! Make a backup (using the a5 built in tools) OF A WORKING DATABASE, and the backup is going to be missing those tables. (Because a5 backups don't backup anything that is "dropped" from the CP.) The backup database won't work because of the missing table (that was merely dropped in the original), and there is no way to fix it/get it back! (Unless you have the original somewhere which still has the dropped objects sitting in the directory.)

    Note: I've always thought (and suggested several times) that the backup/zip routine (by default) should provide the ability to back up dropped objects! ~ I had recommended that Alpha added a checkbox to the zip/backup routine which is by default, "checked." (I submitted this as a bug/suggestion/request several years ago.) And while this wouldn't fix the issue of sets not realizing a table has been dropped, it would ensure (by default) that you get a backup of the entire "working" database. (A backup including the dropped table which you could re-add.)

    It seems to me, the backup/zip routines need to be modified as suggested! Ultimately, this scenario renders the zip/backup routines useless!

    Because of this "problem", I'll bet there are a few zipped databases "out there" that are useless without the originals! (And nobody will realize this until a catastrophic failure occurs & they need to restore from scratch!)
    Last edited by SNusa; 01-26-2013, 10:15 AM.
    Robert T. ~ "I enjoy manipulating data... just not my data."
    It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
    RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."


    • #32
      Re: v.11 Desktop Anomalies & bug list (legitimate contributions welcome from all)

      Originally posted by Tom Henkel View Post
      Regarding the vertical scroll bar issue.

      It may not be completely corrected, but Alpha DID make a correction to the vertical scroll bar issue which actually severely impacted us. They created a calculation that gets done on every movement up or down the browse. This calculation rendered our browses inoperable. Many of our tables are VERY large (>100K records), and this calculation for each record passed through brought the browse display to its knees. We were advised by Selwyn to turn off the recalculation, and we are now able to use browses. Alpha worked with us to pinpoint the issue and quickly got us the fix.

      Hi Tom, I know this is a very old post, but can you explain what you mean by 'turn off the recalculation'?