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

What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

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

    What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

    I have some WEB apps running using v3.5 Build 2999.
    I'm going to be upgrading to v4.3.2 Build 4099.

    What do I need to do to have a seamless upgrade? Will I need to republish the files?
    Everything is working so well. I would hate to break things with an upgrade.

    Thanks
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

    #2
    Re: What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

    Why upgrade? Why upgrade to a version that is almost a year old?

    There are about 5000 changes between 2999 and 4099. About 5000 more between 4099 and the current release.

    Will you have a seamless upgrade? I'd be shocked if you did. I'd be shocked if you expected it.

    Everything is working so well.
    Doesn't this give you a partial answer?

    If you are going to update, then update to the latest release. And update to a test server and spend the time testing your application before releasing it.

    Comment


      #3
      Re: What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

      You will almost certainly run into things that need attention. But there's no way to know what they'll be from here. A republish of components may solve some of the problems as you encounter them.

      The "problems" are seldom Alpha issues really, but things not quite tight enough on your end that suddenly show up when you make a jump of this size.

      But, better now than waiting until you're even further behind. And, you really ought to go with the most current release.
      -Steve
      sigpic

      Comment


        #4
        Re: What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

        I'll give you an example. I just upgraded by biggest project 24 hours ago, hadn't done it for some time. It seems that every list control with an onSelect event needs to be edited to setTimeout() to 50 or 100 ms. Every darned one of them. And I don't don't know why.

        And, 24 hours after starting, I'm still not finished fixing all the "little" things we've discovered.

        - Steve
        -Steve
        sigpic

        Comment


          #5
          Re: What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

          Originally posted by Steve Workings View Post
          I'll give you an example. I just upgraded by biggest project 24 hours ago, hadn't done it for some time. It seems that every list control with an onSelect event needs to be edited to setTimeout() to 50 or 100 ms. Every darned one of them. And I don't don't know why.

          And, 24 hours after starting, I'm still not finished fixing all the "little" things we've discovered.

          - Steve
          Sounds familiar ... there was a bug a while back where the onSelect would erroneously fire when the UX rendered. I believe Alpha fixed it unless I'm mistaken.
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant​​

          Comment


            #6
            Re: What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

            I upgraded to the last official build 4624_4981 (v4.5.1). Unlike some, I don't have time to keep up with all the release notes, pre-release notes, and bug notes, and besides, what else to do as Alpha doesn't support pre-releases? At least I figured out the cause and solution pretty quickly.

            Another bit of fun: It's been typical for me and a couple guys I work with to leave the data source for a list defined as [] and then fill it with json at runtime. That's not happy any more - you need at least one json record defined in the data source now.
            -Steve
            sigpic

            Comment


              #7
              Re: What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

              Why upgrade? Why upgrade to a version that is almost a year old?

              There are about 5000 changes between 2999 and 4099. About 5000 more between 4099 and the current release.

              Will you have a seamless upgrade? I'd be shocked if you did. I'd be shocked if you expected it.
              Why upgrade? To take advantage of newer features available.
              A year old version? $$$$ my license will only allow for build 4099.
              Seamless, no. I was hoping people could give me some known issues.

              On the desktop side, there were few issues when upgrading and they were generally known.
              Steve is giving me some of what I was looking for.
              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


                #8
                Re: What kind of trouble will I get into if I upgrade from Build 2999 to Build 4099

                For what it is worth, I would update the server and start going through the components - if one fails try to save it with the new version and upload - this may or may not solve the issue. If it does not and you cannot solve it, revert back. I would not recommend a mass recalculate, as you will not know what gets fixed and what didn't.
                Reverting back seems to work great for me, especially because I know I can restore a previous version of a component if all else fails. I do not think you will have much of an issue.
                As was said earlier, you might find some small issues like perhaps some list layouts have changed - but they can be easily fixed. If you do have an issue, it shoudl rear it's head right away allowing you to revert back in a snap.
                Like I said, install the latest server version and see what happens prior to recalculating any UX components.
                NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                Comment

                Working...
                X