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

Problems after downgrading to 2999_4519

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

    Problems after downgrading to 2999_4519

    I updated last week to 3522_4647 but discovered some problems (Alpha already knows and from what I hear is working on them) so I downgraded back to 2999_4519. I then discovered that many of my components were empty. All of the controls were gone yet the file size appears to be unchanged. I tried restoring a backup but received an error (it's below). I tried recalculating controls but received some other error (sorry, no screenshot of it). So I again upgraded to 3522_4647 and now I can see the controls.

    Anyone ever see such a phenomenon?

    ScreenShot_002.jpg
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    #2
    Re: Problems after downgrading to 2999_4519

    I dunno but as far as I can tell v4 is a big flop in my opinion. It messed up my calendar and the way my lists layout, had customers calling me this morning so I rolled back to a server patch from nov 15 -and I'm back!
    Not sure how things got mixed up but the last two pre-releases were similarly botched in my opinion.
    If I can offer a tip, rollback restart, full upload and you should be good...
    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


      #3
      Re: Problems after downgrading to 2999_4519

      Charles, have you sent in any bug reports? I have not seen any come in from you. We can't fix it if we don't know it's broken.

      Mike, I am not aware of this particular issue. However upgrading or recalculating a component is generally a one-way operation.

      Lenny Forziati
      Vice President, Internet Products and Technical Services
      Alpha Software Corporation

      Comment


        #4
        Re: Problems after downgrading to 2999_4519

        Originally posted by Lenny Forziati View Post
        Mike, I am not aware of this particular issue. However upgrading or recalculating a component is generally a one-way operation.

        Thanks Lenny. I didn't realize that. Ugh...
        Mike Brown - Contact Me
        Programmatic Technologies, LLC
        Programmatic-Technologies.com
        Independent Developer & Consultant​​

        Comment


          #5
          Re: Problems after downgrading to 2999_4519

          Lenny, your right I havnt sent in any bug reports - I was just complaining which probably isnt fair but I am, and to be fair Alpha ALWAYS addresses my concerns and issues. I am sending one in this morning. I have an issue with images in a list control, and another in my calendar component (Jims) but he is looking into that for now - but I firmly beleive it is an Alpha issue as the calendar fails only with the last two "pre-releases", one of them being the last official update.
          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


            #6
            Re: Problems after downgrading to 2999_4519

            Also, in conversing with Jim Coltz it looks like there WAS a change at build 4575 that may affected his calendar related to session variables. My statement saying the release was a "flop" was harsh stemming from my frustrations dealing with people upset at me after I upgraded. If indeed, I need to make some adjustments due to the way session variables work, it would have been awesome to know that but admittedly it is impossible to know the many ways we use Alpha and the quirks we introduce ourselves.
            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


              #7
              Re: Problems after downgrading to 2999_4519

              Originally posted by mikeallenbrown View Post
              I updated last week to 3522_4647 but discovered some problems ... so I downgraded back to 2999_4519. I then discovered that many of my components were empty. All of the controls were gone yet the file size appears to be unchanged. I
              Yes, I saw this problem with a component someone posted on the board where I was on build 2689 and the posted component was something like build 33XX.

              How did you do the downgrade? I tried twice to do an un-install by running the uninstaller that Alpha leaves behind. You run it by passing it the file name of the install .log file. But it crashes and does not do a complete un-install. I think I reported this as a problem years ago. It's time they replace the installer. Anyway, I ran all the un-installers for all the builds I had installed into separate folders past build 2689. Then I manually deleted remaining files and folders. There is also a "common" folder that probably has to be removed when downgrading.

              Comment


                #8
                Re: Problems after downgrading to 2999_4519

                Like Lenny said, "However upgrading or recalculating a component is generally a one-way operation."

                Until this morning I thought I could upgrade and if I an into problems simply downgrade. I thought wrong. Going forward I'll be backing up my entire web project folder prior to apply patches/updates.

                To downgrade I just delete the A5V12 folder and reinstall using the full installer.
                Mike Brown - Contact Me
                Programmatic Technologies, LLC
                Programmatic-Technologies.com
                Independent Developer & Consultant​​

                Comment


                  #9
                  Re: Problems after downgrading to 2999_4519

                  To roll back to an earlier build, all you need to do is install the patch for the build you want to use. The patches include everything but support files that are not build specific.

                  Comment


                    #10
                    Re: Problems after downgrading to 2999_4519

                    I have always been able to do with great success just as Jerry is stating. If I run into an issue with a pre-release all I need to do is install the last patch that worked and as I said in an earlier post - roll back, upload, and im back! Sometimes you will need to restart the system, and although I have always thought that - that means restart your alpha anywhere server - I have found that I needed to restart the system. One thing is for sure, I have not had an issue that I could not QUICKLY recover from.

                    On that note, I owe Alpha software and it's employees an apology. V4 is NOT a flop, in fact it's awesome - in my frustration, I completely over reacted here. Factually, I made a bad choice of words. I did have an issue, however it was easily fixed AS USUAL.

                    Sorry guys!
                    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


                      #11
                      Re: Problems after downgrading to 2999_4519

                      The reason that all of the controls appear to be gone when going from V4 back to V3.5 is that V4 uses a newer format to store the component definition. However, in this case it is not a one-way conversion as I had previously indicated.

                      If you open the component in V4, go to properties and scroll down to the bottom you can set the Save component format from "Formatted JSON" (the newly added format, back to "Binary" and save your component. You will then be able to use it in V 3.5 again.

                      ComponentSaveFormat.png

                      Lenny Forziati
                      Vice President, Internet Products and Technical Services
                      Alpha Software Corporation

                      Comment


                        #12
                        Re: Problems after downgrading to 2999_4519

                        Mike, in regards to your first post: I have not seen a problem with trying to restore an individual component from Alpha's built-in right-click context menu "Restore Backups" option. But I have not tried restoring a component from a higher build version. I would think the error message you posted, means that Alpha can't find any backup files for the selected component.

                        For those that may not know, the individual component backups exist as individual files in the "_backup.backup" folder under your project folder, unless you have specified an alternate location using the Web Projects Control panel / "Project Properties", "Design-time Properties", "backup folder". Every time a component is saved a backup is created in that folder. For Components, the backup file names begin with a guid that comes from the "tmpl.GUID" variable in the component. You can find the guid for any particular component by opening it and clicking the "xbasic" tab along the bottom, by the "Settings" tab, and then searching for "tmpl.GUID". The file names in the "_backup.backup" folder are suffixed with "_N" and a seven digit ascending number and ".backup".

                        In addition to using these individual component backups, it is also convenient to have alpha make a daily backup of the entire project when you first open it each day. Do this through "View / Settings" , Workspace / Backup, "Require periodic backups every 1 day" and "X - Require user to backup workspace".

                        Comment


                          #13
                          Re: Problems after downgrading to 2999_4519

                          Oh, I see from Lenny's post the internal format has changed of the components. Perhaps that is why Component Restore won't work in an older Build on newer saved components. Perhaps restore is trying to verify the internal GUID number of the component and it doesn't know how to read the new JSON format? So, it is really nice there is a way to save the component in the old binary format, as Lenny posted. I think I'm really going to like the JSON format when it comes to version control systems and being able to do a type of text compare between two versions of a component.

                          Comment


                            #14
                            Re: Problems after downgrading to 2999_4519

                            Originally posted by Lenny Forziati View Post
                            The reason that all of the controls appear to be gone when going from V4 back to V3.5 is that V4 uses a newer format to store the component definition. However, in this case it is not a one-way conversion as I had previously indicated.

                            If you open the component in V4, go to properties and scroll down to the bottom you can set the Save component format from "Formatted JSON" (the newly added format, back to "Binary" and save your component. You will then be able to use it in V 3.5 again.

                            [ATTACH=CONFIG]41859[/ATTACH]
                            Thanks Lenny! ...makes sense!
                            Mike Brown - Contact Me
                            Programmatic Technologies, LLC
                            Programmatic-Technologies.com
                            Independent Developer & Consultant​​

                            Comment


                              #15
                              Re: Problems after downgrading to 2999_4519

                              Originally posted by CharlesParker View Post
                              I have always been able to do with great success just as Jerry is stating. If I run into an issue with a pre-release all I need to do is install the last patch that worked and as I said in an earlier post - roll back, upload, and im back! Sometimes you will need to restart the system, and although I have always thought that - that means restart your alpha anywhere server - I have found that I needed to restart the system. One thing is for sure, I have not had an issue that I could not QUICKLY recover from.

                              On that note, I owe Alpha software and it's employees an apology. V4 is NOT a flop, in fact it's awesome - in my frustration, I completely over reacted here. Factually, I made a bad choice of words. I did have an issue, however it was easily fixed AS USUAL.

                              Sorry guys!
                              I hope you can now continue your life.

                              Comment

                              Working...
                              X