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

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

Backup macro issue in V7.02

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

    Backup macro issue in V7.02

    When programming a backup via a macro, every time I am told about needing another diskette, the backup aborts with a compression not successful message. If I do the same thing at the keyboard, it works fine.

    If anyone knows how to program a multi-disk backup, your help would be greatly appreciated.

    #2
    RE: Backup macro issue in V7.02

    Hans;
    I don't have an answer to your question, but just in case you are not aware of it, as I understand it, the backup routine for A4v6 (and hence also A4v7) is not "guaranteed" for multi-disk backup i.e. there is some sort of bug in it and "occasionally" a full back-up across multi-disks is not fully accomplished. You should be aware of this for critical data. When V7 first came out, I asked whether this "bug" had been addressed, and the answer was that there had been no changes. I believe the backup routine was developed by a 3rd party who is no longer in business.

    Duncan

    Comment


      #3
      RE: Backup macro issue in V7.02

      Hans:

      The best backup is one that you create in a script using Pkzip from the command shell available in Alpha4. Pkzip's prompts for the additional disks will screen in that shell window giving the user a chance to insert the next consecutive disk.

      Like others, I've found early on that the backup in the Alpha software is not reliable.

      Ken

      Comment


        #4
        RE: Backup macro issue in V7.02

        Thanks Ken and Duncan. Ironically, I had originally used PKzip for him. It was his migrating to a new PC running winXP that required the Alpha 4 and seemingly now PKzip upgrade. I found that the version my friend had no longer accepted parameters from the command line under WinXP. I'll look for the WinZip XP version. Thanks again.

        Comment


          #5
          RE: Backup macro issue in V7.02

          Hans,

          I did a multi-disk backup for one customer. What you are missing are the intervening keystrokes between the disk changes. I ran a keystroke script while doing a multi-disk manual backup to figure this one out and find the keystrokes needed.

          You can break out of the script and allow the user to input his pausekey to get the second disk started with these keystrokes, then continue looping through this process until the disk is done.

          Because the Alpha 4 backup uses a formatting backup process, you need to have floppies with known good media and no bad sectors. Often today's floppies will have a bad area which will scramble the backup process for the file that falls upon the bad sector. The Alpha Restore process tends to dump out at this point rather than continue.

          You may test your floppies by reformatting them with the /U parameter which should give you a full format and read testing. Reject any floppies that have any bad sectors. Floppies with no bad sectors should be fine for use with the Alpha 4 backup process.

          The use of PKZip is a valid alternative.

          Dave

          Comment


            #6
            RE: Backup macro issue in V7.02

            Thanks Dave.

            Comment

            Working...
            X