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
Devcon 2020 Goes Virtual! LEARN MORE >

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

When updating runtime If I Change a Form then I must copy these files?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    When updating runtime If I Change a Form then I must copy these files?

    Has anyone put together something to help us old guys like�
    If forms, browses, or etc are changed then
    Copy .ddd .ddm & .ddx
    And to be safe copy .set .sem & .sex
    End if
    What is a etc? (from help file)

    If users are on the system � then what
    How to make sure no users are on system?

    If changes are made to web then
    Republish & don�t try to copy .a5w, .a5wcp, .wcp_settings & .webPublishhistory
    End if

    If scripts or user defined functions, menus, toolbars, bitmaps or import def
    Then copy .alb
    End if

    If fields are added then
    Use a5_add_fields_to_table
    End if
    Else backup & backup before starting.
    I think I am about to .Muf
    Else Rmuf
    Any suggestions of a better approach.
    Thanks
    Old tony
    Tags: None
    #2
    Re: When updating runtime If I Change a Form then I must copy these files?

    Has anyone put together something ....

    I think the problem is that it's difficult to get A5 to update itself. I think this would require a separate application to update another application. Also, how would the second application know where to look for the original files and how would it know where to put them. If you have full control over the system, you could copy them yourself. If you wanted this to work on a user's computer that was in a different state and you've never worked on their system, getting the new files to them, on their system in the right place, then copied to the correct place could be rather difficult. Once you did all that, having them run a self-extracting zip file should be a piece of cake.

    To solve these issues, I just use a 3rd party installer. (I can give you more details but there's probably already plenty on the message board. I use Astrum. Here is one thread where I tell how and why I use it. Also, Bob Houle posted something in that thread that sounds useful but I haven't used it so I can't comment on it.)

    Another solution would be a remote control program like LogMeIn (www.logmein.com) or GoToMyPC. I have my customers install the Free version of LogMeIn and just download any update files from my website. If you don't have a website that you can store the files on, they can buy a full version of LogMeIn for about $60/yr. and that will allow you to transfer files directly. The down side to this (although none of my user have complained about it) is that they need to give you the e-mail address, logmein password, and their computer password so you can log in to their computer. (If they have the full version, you might be able to transfer files even if they just send you a guest invite - which doesn't require you to know the e-mail and passwords - but I'm not sure. I can check if you want me to.)

    If users are on the system – then what....

    Just copy the .dd*, .se*, and .al* files anyway. I've been doing this for a long time and never had a problem. Now, if it's necessary to restructure tables, that's another story.

    If scripts or user defined functions, menus, toolbars, bitmaps or import def
    Then copy .alb

    Better copy the .alm and .alx also! BUT, be aware that this will also overwrite security settings and possibly some other things as well.

    If fields are added then
    Use a5_add_fields_to_table

    I do this in the Autoexec script. Just check first to see if the field is already there and, if not, run the 'add' routine. I'm sure some of my examples for this are also on the message board. In fact, the thread in the link above has a couple examples.

    This requires exclusive access. When this is an issue, I tell my users to get everyone out, install the update, then restart ONE copy of the application. That copy will be able to get exclusive access to restructure the tables. Once the first copy gets to the main menu, everyone else can start their copy again. When everyone else starts, the IF routine will skip the update because the field is already there.

    If somebody restarts before everyone gets out, the autoexec will stop and generate an error because it can't get exclusive access. Nothing else will be hurt except that the rest of the autoexec won't run - unless, of course, you add error traps to check for something like this. (I haven't but probably should.)

    IN SHORT - my solution is (1) use a good install maker program to build and distribute your update file (or, you can just send them the files in a zip or executable zip file if you're comfortable that they know where to unzip them to) and (2) update table structures in the autoexec script.

    Comment

    Previous template Next
    Working...
    X