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

Easyily Backing up your Development work

  • Filter
  • Time
  • Show
Clear All
new posts

  • Easyily Backing up your Development work

    Ever said, "I wish I could get back to where I was an hour age, or 2 hours ago?" All too often, we simply find it too much trouble to make backups.
    There are already several superb articles published about backups, including Tom Cone's article on the site. However, as a developer, my requirements were slightly different than those previously published. I needed a backup system that allowed me to develop set structures, Xbasic scripts, layouts etc. and if I found myself going down a wrong road, then I needed to be able to revert back to where I was earlier. I needed several generations of backup to enable me to take one, or perhaps two steps backwards.
    Whenever I reach what I consider to be a significant landmark in the development, I am able to press a single button that will copy my current "Backup No1" folder files to a folder called "Backup No2" and then copy my current work to "Backup No1" folder. This could easily be extended to further generations if required. If I need to take a step backwards, I then simply use my Windows Explorer to restore the relevant files instead of undoing all the changes that I have made.
    Because of the nature of development work, frequently adding/deleting tables, xbasic was not dynamic enough to provide a full maintenance free solution. I started off with writing a small batch file, this is easily done using the Windows Notepad and saving the file as C:Program FilesA5V4Backup.bat
    Text for Myprogram is as follows:-
    cd"PROGRAM FILESA5V4Myprogram Backup1
    copy *.* "c:program filesa5v4Myprogram Backup2
    cd"PROGRAM FILESA5V4Myprogram
    copy *.* "c:program filesa5v4Myprogram Backup1
    You will notice that the filenames are preceded with a double quote("). This is the Windows95 convention for handling long filenames. You will now need to add the Myprogram Backup1 and 2 folders that will hold your different generations of backup files.
    All that is now left is to include a button or custom menu item, to run the batch file, I use the following Xbasic:-
    response=ui_msg_box("Backup","Backup Myprog?",289)
    IF response=1 THEN
    x = sys_shell("C:Program FilesA5V4BACKUP.BAT ")
    ELSEIF response=2 THEN
    END IF
    The ui_msg_box, prevents inadvertent backups if the button is accidentally pressed. The first time the button is used, all Myprogram files are copied to Myprogram Backup1 folder, the second time, Myprogram Backup1 files are copied to the Myprogram Backup2 folder before the Myprogram files are copied to Myprogram Backup1 folder. Think of it like a filing cabinet where all files are moved down a draw each time it is used.
    Of course there are improvements that can be made, like if you delete a table, its files are still in the backup folders, easily resolved with a few extra lines in the batch file if this troubles you. The first time that you use the .bat file, the window stays open when the backup is complete, if you rightclick on the Control menu icon in the top left of the window, the Program Properties box appears, there is a Program tab that allows you to "Close on Exit". The file will then run and close itself when complete. You could also write the batch file to only selectively copy the A5 program files, but not the .dbf files if the Data files are very large, and if all you are interested in is working on the program files. I have only used this on Win95, but expect it would work equally well on Win98.
    The example shown above is simple, only a few lines of batch file text and Xbasic, takes a few minutes to set up, and could save you lots of grief. When the program is complete and ready for your client, simply remove/hide the button. The batch file will of course also work from a shortcut onto your desktop if you so desire.
    Hope some of you can make some use of it
    David Priest
    Alpha Software Consultant
    DP Services, UK