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

x basic and action scritping

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

  • #31
    Re: x basic and action scritping

    Hi Ken,
    Originally posted by forskare View Post
    Why does AS incerts the %%? Perhaps it's a bug. You might want to explore that a bit more.

    .......It only means the environment has been changed and a correction must be made.
    Whether you know it or not, you have indicated a real important difference.

    When you have a piece of code in XBasic, it's code is always the same each time you open it up for editing. This is not true for action script code.

    The moment you load an action script and open up any action, the action script dialog settings are evaluated and new code is generated. So let's say you created in release "X", but are now editing in release "Y". Saving the AS will generate the code per the new releases' AS generating code. So even if you did not change anything, a small edit of an AS line followed by a save, can result in potentially different (and untested) code!

    A similar thing could occur in the way a function works in an Xbasic piece of code operates, but at least with XBasic code, your code would not have changed! Also, it is much less likely that a function would change in a bad way in what it does, versus the code that AS might generate.

    So, one could argue that the prudent thing to do would either change the code to XBasic so that it will not change, or make sure the underlying Xbasic code you start with, is the code you end with (except for your changes) when you edit in a new release.
    Regards,

    Ira J. Perlow
    Computer Systems Design


    CSDA A5 Products
    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
    CSDA Barcode Functions

    CSDA Code Utility
    CSDA Screen Capture


    Comment


    • #32
      Re: x basic and action scritping

      Ken: I love AS, without it I would be lost in space.

      Comment


      • #33
        Re: x basic and action scritping

        Originally posted by forskare View Post
        ....
        Why does AS incerts the %%? Perhaps it's a bug. You might want to explore that a bit more.
        I guess this is really for Gaby H:

        Note that the release notes indicate that Build 2053-3256, 26 Feb had a number of fixes/changes related to email functions. If you got the %% when you patched to this build, that would make it even more plausible to suspect a new bug. It should be easy enough to test. Just go back to an earlier version to verify what happens there with an AS created button. Then come back to Build 2053-3256 (or later) and try it again. If you still get the %%, that is enough reason to submit a bug report even if it should turn out that something else is going on, perhaps related to Outlook. Just try to make your bug report clear and detailed enough that they can repeat the problem.

        By the way, no one said AS is 100% reliable, but for somewhat different reasons neither is Xbasic coding. In any case, I have at least one very old app (circa v4) that has lots of AS in it and it is still chugging along with virtually no need yet to go back and fix AS things that no longer work. Admittedly, part of that is luck though because things do change (for example, Cancel() used to work differently than it does now in certain contexts--and it is not AS per se!).

        Comment


        • #34
          Re: x basic and action scritping

          I read about %% substitution for the @ problem in a thread a long time ago (version 8 and could have even been version 7)...and it happens in version 8 consistently using AS. I thought it was reported at that time and even if it had been and subsequently fixed, it could have been broken again with a patch. I too recommend another bug report for this.
          Mike
          __________________________________________
          It is only when we forget all our learning that we begin to know.
          It's not what you look at that matters, it's what you see.
          Henry David Thoreau
          __________________________________________



          Comment


          • #35
            Re: x basic and action scritping

            Originally posted by csda1 View Post
            When you have a piece of code in XBasic, it's code is always the same each time you open it up for editing. This is not true for action script code.

            The moment you load an action script and open up any action, the action script dialog settings are evaluated and new code is generated. So let's say you created in release "X", but are now editing in release "Y". Saving the AS will generate the code per the new releases' AS generating code. So even if you did not change anything, a small edit of an AS line followed by a save, can result in potentially different (and untested) code!
            Hello Ira,

            Thanks for the insight. I was not aware that AS generated the code each time it is run. I thought that once the code was generated, that was it. I will be doing things just a weeeeee bit differently.

            kenn
            TYVM :) kenn

            Knowing what you can achieve will not become reality until you imagine and explore.

            Comment


            • #36
              Re: x basic and action scritping

              This also clears up possibly some causes of user problems when just the simple conversion of an AS to xbasic or completely recreating the AS cures the problem when just modifying the current errant AS code will not. Good thing this doesn't happen on a regular basis!! Definitely something to keep in mind.
              Mike
              __________________________________________
              It is only when we forget all our learning that we begin to know.
              It's not what you look at that matters, it's what you see.
              Henry David Thoreau
              __________________________________________



              Comment


              • #37
                Re: x basic and action scritping

                Hi Kenn,

                Originally posted by forskare View Post
                Thanks for the insight. I was not aware that AS generated the code each time it is run. I thought that once the code was generated, that was it. I will be doing things just a weeeeee bit differently.
                Just to be clear, it is not when you run it, it is when it is being edited.

                It is regenerated when you open an action line in an action script for editing and click finish (but not when you hit cancel while editing the line). I believe it only regenerates the current edited action script line, so the other action script lines are probably not (95% certainty) regenerated. You'll know it's been regenerated, because you'll see an asterisk next to the code's tab. When you do a save of the code's tab, is is saved in the database's dictionary.
                Regards,

                Ira J. Perlow
                Computer Systems Design


                CSDA A5 Products
                New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                CSDA Barcode Functions

                CSDA Code Utility
                CSDA Screen Capture


                Comment


                • #38
                  Re: x basic and action scritping

                  Originally posted by csda1 View Post
                  ....
                  Just to be clear, it is not when you run it, it is when it is being edited....
                  Which, in this regard means it does not make much if any difference whether one uses AS or Xbasic. Clearly if one edits an AS line, one surely is going to test it to make sure it still does what is desired, no?

                  This whole discussion reminds me of something I alluded earlier in this thread: From one release (including patch updates) to another many things other than AS code can and do change. For example, a few years ago one could prevent a red X click from closing a form by simply putting "Cancel()" in the form's CanExit event, forcing the user to click a button that did something prior to coming to parentform.close() which then closed the form. Then at some point either the details of what Cancel() does changed or what happens when a CanExit event fires changed and from then on even parentform.close() would not close the form (as it probably never should have, i.e., that it did was probably a bug that was eventually fixed).

                  The point is that it is not just the coding behind AS that may change from time to time, virtually anything is subject to change. Which means if you are looking for something that is 100% reliable in the sense that it will always and forever work, AS coding is hardly the only thing that is going to disappoint you. To repeat, new users should use AS both to accomplish things and, by converting AS to Xbasic, as a good way to learn Xbasic and especially Xdialog. And no, I did not say this was the only way to learn Xbasic or that the Xbasic code generated by AS is as good as can be done. But it is a tremendous tool in the Alpha Five toolkit.

                  Raymond Lyons

                  Comment


                  • #39
                    Re: x basic and action scritping

                    Originally posted by Raymond Lyons View Post
                    Which, in this regard means it does not make much if any difference whether one uses AS or Xbasic. Clearly if one edits an AS line, one surely is going to test it to make sure it still does what is desired, no?

                    This whole discussion reminds me of something I alluded earlier in this thread: From one release (including patch updates) to another many things other than AS code can and do change. For example, a few years ago one could prevent a red X click from closing a form by simply putting "Cancel()" in the form's CanExit event, forcing the user to click a button that did something prior to coming to parentform.close() which then closed the form. Then at some point either the details of what Cancel() does changed or what happens when a CanExit event fires changed and from then on even parentform.close() would not close the form (as it probably never should have, i.e., that it did was probably a bug that was eventually fixed).

                    The point is that it is not just the coding behind AS that may change from time to time, virtually anything is subject to change. Which means if you are looking for something that is 100% reliable in the sense that it will always and forever work, AS coding is hardly the only thing that is going to disappoint you. To repeat, new users should use AS both to accomplish things and, by converting AS to Xbasic, as a good way to learn Xbasic and especially Xdialog. And no, I did not say this was the only way to learn Xbasic or that the Xbasic code generated by AS is as good as can be done. But it is a tremendous tool in the Alpha Five toolkit.

                    Raymond Lyons
                    :) Well said!!! :)

                    kenn
                    TYVM :) kenn

                    Knowing what you can achieve will not become reality until you imagine and explore.

                    Comment


                    • #40
                      Re: x basic and action scritping

                      Hi Raymond,

                      Originally posted by Raymond Lyons View Post
                      Which, in this regard means it does not make much if any difference whether one uses AS or Xbasic. Clearly if one edits an AS line, one surely is going to test it to make sure it still does what is desired, no?
                      Despite the surface appearance that they are the same, they are actually radically different. A function (Alpha's or a user's UDF has code that is syntactically compiled without errors (otherwise it would never be able to be used) and tested for what it is.

                      Some AS actions are very simple and straightforward. These seldom have issues, as there is almost a 1 to 1 correspondence to the XBasic code they generate. Others actions generate code from many selections of menus and settings. These generate a string of code that needs to be compiled (which Alpha does when you save it) without errors, and more importantly makes sense for all the settings. While, in general, each setting (or multiple settings) of an action script builds a portion of the code, there is no way every combination of possible codes could ever be fully tested. Some parts can be very straightforward to generate (and to test - this is why it generally works) and other parts depend on multiple settings which can be a nightmare to generate and can create extremely complex code.

                      In most cases, there is a very specific code generation sequence where you take setting "A", generate it's code, take setting "B" append it's generated code and so forth. But then there are cases where "B" implies what "A" generates, and where it needs to be located in the code, and so forth. It can get so intertwined, that it's impossible to totally predict what it will or could generate and these are where the typical failures tend to be.

                      That doesn't negate the usefulness of AS, but it does significantly increase the chance of generated code that won't work because of the settings.
                      Regards,

                      Ira J. Perlow
                      Computer Systems Design


                      CSDA A5 Products
                      New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                      CSDA Barcode Functions

                      CSDA Code Utility
                      CSDA Screen Capture


                      Comment


                      • #41
                        Re: x basic and action scritping

                        Originally posted by csda1 View Post
                        Hi Raymond,



                        Despite the surface appearance that they are the same, they are actually radically different. A function (Alpha's or a user's UDF has code that is syntactically compiled without errors (otherwise it would never be able to be used) and tested for what it is.

                        Some AS actions are very simple and straightforward. These seldom have issues, as there is almost a 1 to 1 correspondence to the XBasic code they generate. Others actions generate code from many selections of menus and settings. These generate a string of code that needs to be compiled (which Alpha does when you save it) without errors, and more importantly makes sense for all the settings. While, in general, each setting (or multiple settings) of an action script builds a portion of the code, there is no way every combination of possible codes could ever be fully tested. Some parts can be very straightforward to generate (and to test - this is why it generally works) and other parts depend on multiple settings which can be a nightmare to generate and can create extremely complex code.

                        In most cases, there is a very specific code generation sequence where you take setting "A", generate it's code, take setting "B" append it's generated code and so forth. But then there are cases where "B" implies what "A" generates, and where it needs to be located in the code, and so forth. It can get so intertwined, that it's impossible to totally predict what it will or could generate and these are where the typical failures tend to be.

                        That doesn't negate the usefulness of AS, but it does significantly increase the chance of generated code that won't work because of the settings.
                        :D WHEW!!!
                        TYVM :) kenn

                        Knowing what you can achieve will not become reality until you imagine and explore.

                        Comment

                        Working...
                        X