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

A5 ver 6 crash on Script run command

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

    A5 ver 6 crash on Script run command

    Hi
    We moved from ver 5 to ver 6 last August and had quite a few
    problems with the transfer, particularly running long established
    ver 5 scripts.
    However nearly all problems were solved with the help of this terrific
    bulletin board and Ver 6 has proved invaluable in automating so much FTP work to and from our web site.
    However one problem with ver6 was never solved and we just work
    around it by loading ver5!

    When I run this script/scripts on my home development machine on ver6
    it works both in a runtime version and the full version.
    I have 3 scripts. The master script makes calls on two other
    scripts with the usual command
    script_play("compile_forma")
    script_play("compile_formb")

    However when the same script/scripts are run on two different computers
    in our office on a runtime versions of ver6, it fails at the command - script_play("compile_forma")
    with the error "expected value".

    Hwoever on the runtime version of ver5, it functions perfectly on all computers!
    We cant move from ver 5 till I solve this. Grateful for any suggestions!

    #2
    We're going to need to see the contents of compile_forma in order to offer any assistance.

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

    Comment


      #3
      Lenny is of course correct. I believe V6 was the point at which arrays must be referenced with somearray[] syntax while prior versions could use that or somearray().

      Just a thought.
      There can be only one.

      Comment


        #4
        Many thanks

        What stumps me is it works perfectly on ver6 on my home development
        machine in both runtime and full versions.

        It just refuses to work on other machines which have runtimes of ver6.

        Regarding the ( and ] arrays. Yes, we had fun changing all those last year

        Comment


          #5
          Kevin, on the theory that the simplest possibility is sometimes correct, double check the A5v6 builds being used on the non-working machines. Are they the same as the builds on your home development machine ? -- tom

          Comment


            #6
            Good thinking Tom

            Will check this first and get back.

            Comment


              #7
              Tom

              Have downloaded the latest Ver6 Runtime and
              installed on all machines. The build number is
              5.1 build 1555

              Result still the same. Runs program runs ok on the development machine
              but when using run time versions on different computers,
              Alpha fails at the command -
              script_play("compile_forma")
              with the error "expected value".

              Comment


                #8
                Hi Kevin,

                As stated by Lenny:

                We're going to need to see the contents of compile_forma in order to offer any assistance.
                Good luck
                Cheryl
                Cheryl
                #1 Designs By Pagecrazy
                http://pagecrazy.com/

                Comment


                  #9
                  Be please to supply.
                  How is required. By email?

                  Comment


                    #10
                    Originally posted by kgilroy
                    Be please to supply.
                    How is required. By email?
                    Open Alpha
                    Go to the control panel, code tab.
                    Open the script in design mode.
                    Right click in script editor, choose write to file, note name and where saved.
                    Respond again to this thread.
                    Scroll down below reply box and choose "Manage attachments."
                    Attach the file.
                    There can be only one.

                    Comment


                      #11
                      Originally posted by kgilroy
                      Tom

                      Have downloaded the latest Ver6 Runtime and
                      installed on all machines. The build number is
                      5.1 build 1555

                      Result still the same. Runs program runs ok on the development machine
                      but when using run time versions on different computers,
                      Alpha fails at the command -
                      script_play("compile_forma")
                      with the error "expected value".
                      Are you using a variable named result?
                      Tommy Thompson
                      Thompson Consulting Services
                      Beautiful Kentucky Lake, Springville, TN 38256
                      [email protected]

                      Comment


                        #12
                        Many Thanks

                        script is attached.

                        Comment


                          #13
                          Many thanks Tommy.

                          No, no variable used called result.

                          Comment


                            #14
                            Hi Kevin,

                            Unfortunately your code is beyond me. I am bowing out of this issue to allow our xbasic guru's further assist you :)

                            Good luck
                            Cheryl
                            Cheryl
                            #1 Designs By Pagecrazy
                            http://pagecrazy.com/

                            Comment


                              #15
                              Kevin, I took a look at your code. It looks like a subroutine that would be called from a second program, perhaps lots of times in a row. It's not free standing and relies on other code you have not shown us to open the data table(s) and fetch through the records.

                              You mention there are actually 3 scripts, with one calling the other 2. This suggests a couple of more ideas for you:

                              1) Since you don't set a different scope for the variables in "compile_form_a", you may have a scoping issue. Frankly, this seems unlikely, but I thought I'd mention it.

                              2) A more likely issue is with timing. Especially if you call this script and "compile_form_b" over and over in a tight loop as you fetch through records in one or more tables. The fetch over the network will take longer than the fetch on your home development system. I'd build in some pauses so that the script doesn't get ahead of hardware. Xbasic_wait_for_idle() at the end of each iteration would be a good starting point. If the 3rd script uses the same table(s), I'd force the calling script to wait until the 2d script is finished with them. Otherwise, you have the 2d and 3rd scripts running concurrently. I can imagine cases where this would be ok locally, but would cause problems over a shared network.

                              -- tom

                              Comment

                              Working...
                              X