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

update runtime scripts live

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

    update runtime scripts live

    I am having to do some development using the active production system tables and data files. As users encounter errors in scripts (they are on Run Time), I can correct them, but this does not immediately update their code library as it does in Dev. Is there a method to update code libraries for users that are active on Run Time without them having to log off and log back in? Thanks.
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    Re: update runtime scripts live

    If you are using AEX files you might be able to reload them...Cal Locklin would be the one to ask.
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #3
      Re: update runtime scripts live

      If you are working with the master tables on a server,
      if the users are running shadowed,
      assign a new version number.

      Anytime I make changes I assign a new build number.

      Code:
      dim vAppVersionNumber as N
      vAppVersionNumber = val("1."+buildno)
      
      if a5_getappversionnumber() <> vAppVersionNumber then
      	a5_setappversionnumber(vAppVersionNumber)
      end if
      The next time the user closes and opens the application, I force their shadow database to be updated.
      Alpha 5 Version 11
      AA Build 2999, Build 4269, Current Build
      DBF's and MySql
      Desktop, Web on the Desktop and WEB

      Ron Anusiewicz

      Comment


        #4
        Re: update runtime scripts live

        Hi Ron,
        I think he wanted to avoid them having to log out of the app. But he could offer them a button that would refresh the shadow manually. And like you said, he would have to change the version number.

        I put my scripts in ALB files that load with the app. If these files are on the server, that might pass any script changes to the desktop...but of course wouldn't help update any scripts added to forms.
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment


          #5
          Re: update runtime scripts live

          Hi Guys,
          The entire app is on the server and the users access through Remote Desktop and not shadowed. Each has a shortcut to open the app in RT. And you are correct Robin. I would like the users to not have to log out and log back in. We are small enough now that that is a quick text message or email communication, but I'd like to figure out another way.
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


            #6
            Re: update runtime scripts live

            Mike, I'm not sure how you are accessing the data. If the users are connecting through RDP and are not shadowed, then any changes you make should be instantaneous.
            Are the users opening another instance of the application? You say RDP, do you mean terminal server?

            I would think that it could be dangerous to make changes if others are logged in so they must be running in their own instance of the application.
            I think you could create an OnTimer event which would be checking for a switch that you set. The switch could trigger a message instructing the user to close the app and then open the app.

            If they were running in a shadow, the message could instruct the user to refresh the app from the utilities form.

            I don't know of any other way.
            Alpha 5 Version 11
            AA Build 2999, Build 4269, Current Build
            DBF's and MySql
            Desktop, Web on the Desktop and WEB

            Ron Anusiewicz

            Comment


              #7
              Re: update runtime scripts live

              Hi Ron,
              The server is a terminal server and each user access the server with Remote Desktop and each user opens the application in an individual session with RT. I have in place a modeless dialog that sits on the toolbar that opens on login and has a timer that checks for new system messages that I put out as administrator. However, changes-error corrections to scripts still requires them to log off and back on. I thought there might be a method to have a script that they can update their code library while the app is open and active. I'm guessing now that maybe not.
              Mike W
              __________________________
              "I rebel in at least small things to express to the world that I have not completely surrendered"

              Comment

              Working...
              X