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

error modifying a script?

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

    #31
    Re: error modifying a script?

    I am wrong

    It is back

    Going to stop for the night and tackle again tomorrow when fresher.
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


      #32
      Re: error modifying a script?

      ok
      I have eliminated a lot of things.

      I am including a copy of the db.

      open form finfigures, try to open form variables. After that you will start getting the error from other places. I have managed to fix some of this.

      This form was copied to this db from another db used by v7. it had some of the old code in it that I think I took care of. I had opened it with v7 and removed all the vars, then reinserted them from a notepad file. It seemed to be working to some degree. It now will not open the form vars and once you try, it will start giving the error.

      Please verify this is a bug or me if you can. I will submit if it is a bug.

      .
      Dave Mason
      [email protected]
      Skype is dave.mason46

      Comment


        #33
        Re: error modifying a script?

        Dave, I took a look, I think your form has been irretrievably corrupted.

        Comment


          #34
          Re: error modifying a script?

          me too. I think I may be able to salvage it. It is not easy to write this one. Waste an hour or save 3 days. at least I have the scripts.

          Plan: send it all to a blank db and then clear all with v7 first. Then import it to a v9 db
          Last edited by DaveM; 05-27-2010, 11:43 AM.
          Dave Mason
          [email protected]
          Skype is dave.mason46

          Comment


            #35
            Re: error modifying a script?

            I opened the sample in Alpha v9.
            I could not even see or locate the form(s) in question...have 1 table, "slog", and 3 forms--"enterulog", "fin1", and "financeFigures". Two other tables used to exist dealing with the calendar apparently but not included. Many of the variables on the form "financeFigures" were never set so had 27-28 errors produced when opened.

            So, IOW, not one bit of help available from me this morning!
            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


              #36
              Re: error modifying a script?

              Many of the variables on the form "financeFigures" were never set so had 27-28 errors produced when opened.
              I think that is part of the issue. Those variables are visible in the drag-drop list so they were/are defined somewhere. They are checked in that list so the drag drop list thinks they are indeed on the form. The link between the definitions and the form objects is somehow corrupted.
              There can be only one.

              Comment


                #37
                Re: error modifying a script?

                I sent a bug report.

                if you try to open the form variables in a form and they do not open, you cannot edit a script afterward. this has nothing to do with the previous form. It now affects the other forms too.

                We will see. I hope I hear something back from them.
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment


                  #38
                  Re: error modifying a script?

                  Originally posted by DaveM View Post
                  I am getting this error all of a sudden. Any ideas.

                  edit: It happens in all scripts on this db - have not yet checked others.

                  apparently only one db is affected?? Still lost though

                  edit2: tried it with v7 and v9 with the same result.


                  .

                  it is a bug. there was an undimmed variables in the code that adds the timestamp to the top of a script when you edit it.

                  you have defined a global variable called 'line1' as a numeric.

                  change the name of the variable to something else and the problem will go away (after you exit and restart a5).

                  or you can wait till v10.5 comes out and then you won't have to change your own variable name.

                  Comment


                    #39
                    Re: error modifying a script?

                    I was going to open your zip file, create a new form altogether and test..then I saw Selwyn's response.. No point of opening the zip file or any further testing. Now we know what the "Perfect Storm" scenario is..
                    Last edited by G Gabriel; 05-27-2010, 03:24 PM.

                    Comment


                      #40
                      Re: error modifying a script?

                      It is amazing how fast they found that bug.

                      All the dredit to the Alpha team.

                      Oh, the form is working great now.

                      .
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment


                        #41
                        Re: error modifying a script?

                        Hi Dave,

                        Originally posted by Selwyn Rabins View Post
                        it is a bug. there was an undimmed variables in the code that adds the timestamp to the top of a script when you edit it.

                        you have defined a global variable called 'line1' as a numeric.

                        change the name of the variable to something else and the problem will go away (after you exit and restart a5).

                        or you can wait till v10.5 comes out and then you won't have to change your own variable name.
                        This is exactly the scenario that I have clearly documented in my tips on variable dimensioning.

                        If you use a shared or global (which should be the exceptional case, not the rule), it must be 100% guaranteed to be unique from all of Alpha's code and any other code (e.g utilities like CSDA Code Utility, A5DOC, AIMS App Analyzer, etc), along with every local variable in your code should also be DIM'ed before use, otherwise you are asking for trouble.

                        I have take great pains with all of my utilities to minimize usage to exactly 1 global variable and 1 addin variable, which are both pointers (and dimension everything elsewhere as local and on certain rare occasions as shared). The pointers have many properties values, but because it is all under the unique pointer name, there is never a problem with anyone else's code.

                        While the problem illustrated by your code is now corrected by Selwyn, this is just one of 100's of cases just like this that I know of (and even more that I don't). How much time did you waste on this problem?

                        There are about 1 million lines of code in Alpha's System.aex. I estimate it would take about 6 man-months to fix every DIM reference, and would likely break as many things as it fixed. So realistically, it is not a good idea.

                        But if you had followed my tips, it would never even arisen.

                        P.S. They found the error "so fast" because you provided the code. Without it, it never would be found, because to find it, you needed to create the global duplicate variable name 1st. And it failed exactly at the point I indicated, but was caused by your DIM's and Alpha's not DIMing, which is what I also said, the point of failure is not the cause, just the symptom of something that occurred earlier.
                        Last edited by csda1; 05-27-2010, 05:40 PM.
                        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


                          #42
                          Re: error modifying a script?

                          Ira,

                          I already do know, so deriding me gets us nowhere.

                          Per Selwyn - "it is a bug. there was an undimmed variables in the code that adds the timestamp to the top of a script when you edit it."
                          This variable is in an aex file in the alpha folder
                          The dimmed line1 variable was not the whole the culprit. The aex in the alpha program was broken. That is what the whole thing was about.

                          They found a glitch and they fixed it.

                          In a contract, there are 6 normal lines that have to be exact. Naming accordingly seems natural?? I now have mline1, mline2, mline3, etc to not violate an alpha named variable.

                          I personally am glad it showed up and the bug is done.

                          Have a nice day.
                          Dave Mason
                          [email protected]
                          Skype is dave.mason46

                          Comment

                          Working...
                          X