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

v4.5 -> v5 conversion

  • Filter
  • Time
  • Show
Clear All
new posts

  • v4.5 -> v5 conversion

    What is the best way to convert a 4.5 app to 5? I would imagine that the scripting is where most of the problem resides. I have not started yet. I was hoping someone could point me in a logical direction.

    Tom Lyon

  • #2
    RE: v4.5 -> v5 conversion

    there should be no need to "convert" a v4.5 app to v5.

    if something that works in v4.5 does not work in v5 we would want to know about that so that we can correct it.

    the design goal on v5 was to ahieve 100% updward compatibility. of course, there is always the possiblity that a user was using some extremely esoteric feature, or that the user was relying on some behavior that was actually a bug, and that we have corrected the bug.


    • #3
      RE: v4.5 -> v5 conversion

      I'm not an expert on this, but my understanding is that all you need to do is open your v4.5 app in v5 and that's it. Of course make a backup first, just in case.



      • #4
        RE: v4.5 -> v5 conversion

        All of your forms and layouts should open in V5 just as they do in V4.5. However, if you open a form (don't know about other layouts) in design mode and then save it, it will no longer be designable (?) in V4.5. I would not open my live data in V5 just in case. Instead make a copy of your app including the data and open the copy in V5.


        • #5
          RE: v4.5 -> v5 conversion

          I guess the question was more of a troubleshooting one. I'm more than willing to correct improper syntax, etc., and was hopeful there was some kind of log I could view that told me in descriptive terms where any problems might lie. I have run into two instances (*only* two, that I can see so far) that might warrant your inspection. I will put something together for you to look at.

          Tom Lyon


          • #6
            RE: v4.5 -> v5 conversion

            My script was failing on
            :controlpanel.left = 1
   = 1

            commenting those lines out fixed it.

            The other script error occured upon closing my application. I had been going through some hoops to get Alpha Five to properly close. I removed all of that frivolous code and left *only* :a5.close()..and it worked perfectly. You've certainly fixed that bug well.

            I like the additional right-click menu control available in embedded browses.

            The beta is definitely operating slower. I imagine you have various debugging routines running that will impact speed of operation. I can see this in the trace window.

            Keep up the good work.

            Tom Lyon


            • #7
              RE: v4.5 -> v5 conversion


              One interesting situation I have found working with the beta is that A5V5 will trap errors that are ignored / missed in v4.x. Now, if I am working on an app in A5v4.5, I copy everything to a different directory and open it in V5 and then open every form and run every script. It is surprising the little things it finds. I can then go back into v4.5 and correct the problem in the original copy.

              Selwyn, is correct about the 100% compatibility. The only issues I have had are either bugs still to be fixed (very few) or some quirk (called - poor practice) in the way I was doing something in v4.5 that is easily changed in v5.

              Concerning the speed, when you open a database in v5 for the first time, go to the code editor and open every custom menu and toolbar and resave. V5 uses different methods to build these and resaving will convert them. If you don't, every time a form opens, the menu and toolbar are converted temporarily. Not very efficient or speedy. Once converted, the speed is only slightly slower, depending on the speed and memory of the computer.



              • #8
                RE: v4.5 -> v5 conversion

                I notice that I have to go every form - where I have code to go to another form and find the same CLIENT - and open my code and save it again to work.

                I have lots of forms. Is there a way to update all code at one time at one place?