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

Damage Limitations!

  • Filter
  • Time
  • Show
Clear All
new posts

    Damage Limitations!

    The small company I work for have suspended invoicing customers for three days so that I can replace our old Alpha4 system with Alpha5 V9
    everything was going swimmingly until one of the sets became corrupt (no idea why - but it was after I'd done a back-up)

    Is it difficult to put a runtime version on to another computer and then add stuff to it, (I will have to re-do the corrupt set and design a complicated report all over again), and I can't delay the company not invoicing for any longer.

    Also, could I be doing something wrong when I do a back up, I DON'T select compact databases and I simply back up from my hard drive to our server.

    Re: Damage Limitations!

    I think you aren't getting responses to your question because it contains multiple questions and is a bit vague.

    Do you need help repairing the set?

    Not exactly sure what you mean by "Is it difficult to put a runtime version on to another computer and then add stuff to it". The A5 runtime is the A5 runtime and has nothing to do with the application other than running it. But, of course, one runtime could run many different applications - at the same time even. Some people put the runtime on the workstation and access the data on the server directly. Others put the runtime on the workstation then "shadow" the application. (Personally, I prefer the shadow method but there are other who claim it isn't necessary on a fast network with little other use.)

    If your runtime accesses the application directly on the server, you don't have to "add stuff to it" because it will already be there as soon as you update the server.

    If you shadow the runtimes on the workstations, just go to the A5 control panel in the shadowed version after updating the server and click on "Tools/Refresh Shadow". (Or, you can build a button that calls the Refresh_shadow() function.)

    As for doing something wrong with the backup, I don't see how that would be the problem (and I'm always right;)).


      Re: Damage Limitations!

      Originally posted by Judith View Post
      Also, could I be doing something wrong when I do a back up, I DON'T select compact databases and I simply back up from my hard drive to our server.
      I had a problem after I did a compact and then a backup. I would have all kinds of problems until I would reindex the tables. After I figured out the problems I was having was after using Alpha's backup I stopped backing up with alpha and used one of our other backup programs. Never had those problems again.


        Re: Damage Limitations!

        FWIW, I can't remember the last time I did a "database compact". I hate that function because it always does everything whether it's needed or not. And one half of what it does is for the benefit of the user and the other half is for the benefit of the developer. It packs the tables and re-indexes them whether they need it or not (typically a user need); then it compacts all the data dictionary files (*.dd*, *.se*, <adbname>.al*) whether they need it or not (typically a developer need).

        And, if I recall correctly, it doesn't tell you when something fails to compact because someone still had it open.

        - If I need to pack a table, I pack the table. (My "pack_all" routine for users checks to see if there are deleted records before packing. This can save a lot of time in some cases because it eliminates the automatic re-indexing that shouldn't be needed if there were no records deleted.)
        - If I need to re-index a table, I re-index the table.
        - If I need to compact a data dictionary, I compact the data dictionary. I never provide the user with a "compact dictionaries" routine because they will never need it. When I do an update, I take care of that myself. (The "Compact Dictionaries" option in my AIMS Grab Bag shows which data dictionaries have deleted records that need to be compacted and/or you can look at the last modified date to determine which files you want to compact. Note that compacting data dictionaries does more than just remove deleted records so you can't just go by that. When done, just for fun, it also shows how many bytes have been eliminated.)

        Data dictionaries should never need to be compacted by users and, conversely, the tables seldom need to be packed by the developer. However, the "Database Compact" routine always does both. Packing a large table can take a lot of time while compacting the data dictionaries for that same table will be quite fast. So, if you're a developer and want to keep your data dictionaries clean but don't want to waste a lot of time constantly re-indexing, either get my Grab Bag which has that and a number or other utilities ($19) or build your own routine using Dictionary.Update().

        Also, my AIMS Backup routine (which I include with every app I build) seems to work even if other users are in the database. I've received many backups that were done that way and have never yet found one that was corrupted. (I can't guarantee it will never be corrupted but I've been using it for about 10 years and haven't heard of a problem yet.) For some reason A5's built-in backup will not back up tables that are in use. However, my backup routine does not have any provision for packing tables as part of the backup. I've had too many customer call and ask how to retrieve something they recently deleted and, consequently, I don't want them packing tables without understanding the consequences.