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

Backing Up

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

    Backing Up

    Have adapted Tom Cone's excellent Learn Alpha Automated Back Up Procedures as an add on to my unlimited runtime app. Brilliant!

    My client owns several branches and each branch can now email the data to head office. The bonus is, he now has full running versions and backups for each branch on his main office computer. The operation takes seconds. I am happy to share the technique that I have learnt should any one be interested.

    I have one button to do this which prompts for the floppy and branch name etc but I would like to add an end 'Back Up Complete' message. Does any one know if Xbasic can detect if drive A: has finished writing?

    Michael

    #2
    RE: Backing Up

    Michael, thanks for the compliment. I'm glad it proved useful to you.

    In my own application the backup routine runs in a DOS window, as described in the article. I've changed the batch file commands somewhat to make the process more meaningful to the user.

    Using the echo command you can display lines of explanatory text.

    Using the pause command you can interrupt the batch process altogether.

    Using these in combination I pause the batch process when the backup is complete, and explain to the user how to close the DOS session.

    I do not know how to gracefully determine when the DOS batch file has run its course, but will be 'lurking' about to see if others have suggestions on this.

    -- tom

    Comment


      #3
      RE: Backing Up

      Tom,
      I struggled with the same issue with a DOS based backup routine. My problem was that I used the process to backup data before another operation and I needed to be sure that the backup was complete. The solution was to use the last line of the DOS batch file to copy a dummy file to a specified location. I then used a loop to look for the dummy file. The file only exists when the batch file was complete. When the loop finds the file, the script will continue. A sample of the script is below. Back is the pointer for the DOS batch file (backup_d.bat) which is created by the script. new_path and new_private_path are the paths of the backup batch file location and the A5 private path that have been converted to DOS short form (I created a function to convert from long name to short name)

      '/// lines to create batch file
      back.write_line ("copy "+new_path+"backup_d.bat "+new_private_path+"done.txt")
      back.flush()
      back.close()
      timer = toseconds(time())

      if file.exists(:A5.Get_Private_Path()+"done.txt")
      file.remove(:A5.Get_Private_Path()+"done.txt")
      end if

      sys_shell(:A5.Get_Path()+"backup_d.bat")

      while .not.file.exists(:A5.Get_Private_Path()+"done.txt")
      if toseconds(time()) - timer > 60
      error_generate("Timed Out Error")
      exit while
      end if
      end while
      '/// lines to indicate process is done or additional xbasic processes.

      As you can see, the script will time out after 60 seconds in case the DOS batch file fails. Otherwise the user would have to use A5Halt. This method works very well for me.

      Jerry

      Comment


        #4
        RE: Backing Up

        Ahhhhh! Great idea!

        (Now why is that this kind of thing seems so obvious after it's described, than when we're staring at a blank screen?)

        -- tom

        Comment


          #5
          RE: Backing Up

          It came in my sleep. I was staring at blank eyelids. Less glare. :)

          jERRY

          Comment


            #6
            RE: Backing Up

            Hey guys, why do all this when you can just winzip
            up your A5 folder and attach that to an e-mail as attachment, or write it to a CD, or zip drive or secondary drive (on the server/standalone or on a networked drive. This can be very easily automated in fact.

            Then, if needed just unzip it and you are ready to go.

            In our office we unzip and run the program--nothing like a
            backup that will not work [i am supposing that is why you are checking for that dummy file].

            Is there some advantage that I do not know about?

            P.S. I believe in A5v5 this is made even easier to do.

            Comment


              #7
              RE: Backing Up

              Aside from a personal tendency to do things 'the hard way', I have it set up this way because:

              1) my users are poorly trained, and cannot be trusted to select the right files or folders to backup; and

              2) I want to make it *easy* for them. If it's not easy they won't do it.

              Remember that 'deer in the headlights' look you got the first time you tried to explain to a newbie how their hard disk is organized?

              -- tom

              Comment


                #8
                RE: Backing Up

                Me too, the market that I am aiming at have got no knowledge of Winzip or Windows explorer. Every thing has to be by buttons.

                Michael

                Comment


                  #9
                  RE: Backing Up

                  Also check this this thread on Power Outages for a whole disertation on Backup issues;


                  http://msgboard.alphasoftware.com/alphaphorum/read.php3?sortby=lastreply&direction=desc&num=4&id=23970&thread=23912


                  Regards,

                  Ira J. Perlow
                  Computer Systems Design & Associates
                  [email protected]
                  Regards,

                  Ira J. Perlow
                  Computer Systems Design


                  CSDA A5 Products
                  New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                  CSDA Barcode Functions

                  CSDA Code Utility
                  CSDA Screen Capture


                  Comment


                    #10
                    RE: Backing Up

                    Winzip zips the whole folder and it spans more than one disk, my clients do not want to email the whole app every day so my routine only includes the .dbf, .cdx and .fpt files. Takes seconds.

                    Michael

                    Comment


                      #11
                      RE: Backing Up

                      Some users seem to have enough trouble reading and understanding the buttons. If the operation isn't automatic, it doesn't get done. I even have a script attached to the CanExit event for my main menu that asks if the user wants to backup data. The default button is yes and the default directory is the appication directory. All the user needs to do is hit the ENTER key. Most can do that.

                      Jerry

                      Comment


                        #12
                        RE: Backing Up

                        Jerry,

                        I know users who are still looking for the "ANY KEY" Key! Do you really expect them to be able to find the ENTER key? :?)

                        Michael,

                        You don't need the CDX file either. It can be recreated if need be. The CDX files can get quite large depending upon index key values

                        Regards,

                        Ira J. Perlow
                        Computer Systems Design & Associates
                        [email protected]
                        Regards,

                        Ira J. Perlow
                        Computer Systems Design


                        CSDA A5 Products
                        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                        CSDA Barcode Functions

                        CSDA Code Utility
                        CSDA Screen Capture


                        Comment


                          #13
                          RE: Backing Up

                          Ira, your 'acquaintenances' who are looking for ANY KEY may be related to some I've heard of who think the CD tray was intended as a drink holder for their coffee!

                          -- tom

                          Comment


                            #14
                            RE: Backing Up

                            Ira,
                            An idea - create a blank cdx file (table with no data) and rename as cdb or something similar and back that up. At least the index formats, and expressions, etc are saved.

                            Michael,
                            That explains why I keep spilling my coffee!

                            Jerry

                            Comment


                              #15
                              RE: Backing Up

                              I knew a girl who really liked our fax machine because it gave her a copy of the fax after it sent the other.

                              IN a previous company, a contractor called in and asked why we sent him 20 copies of a fax. When we asked the girl (a different one) she said it was because the fax machine kept kicking out her copy instead of sending it.

                              Comment

                              Working...
                              X