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

Stop endless loop script

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

    Stop endless loop script

    Good afternoon.

    I have a lengthy script that I'm working in the Interactive Window with. It contains an error that puts the script into an infinite loop when run. Haven't found the cause yet. Is there a method to break the loop-stop the script without having to Ctrl-Alt-Delete?

    Thanks,

    Mike W
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    Originally posted by Mike Wilson
    Good afternoon.

    I have a lengthy script that I'm working in the Interactive Window with. It contains an error that puts the script into an infinite loop when run. Haven't found the cause yet. Is there a method to break the loop-stop the script without having to Ctrl-Alt-Delete?

    Thanks,

    Mike W
    I would save the script rather than just working in the interactive and put a debug(1) just after the loop starts. Then you can decide to halt it at any time.
    There can be only one.

    Comment


      #3
      Loosing fetch_next()

      Stan,

      The following script goes through records in a table looking for a particular value and when found it copies fields of that record and enters them to a second table. The script will not hold the increment on the first table and looses the fetch_next(), resets to the first record of the table, after a couple of opening of the second table. I say this because if I remove the script highlighted in red, it increments through the first table appropriately ( the msg_box displays the increments). Is there something in/missing that is detaching the fetch_next() statement? Is there a better way?

      Thank in advance.

      Mike W

      Code:
      ' find mom's alone
      dim demo as p
      dim tbl as p
      dim numchk as C
      dim zfamnum as N=0
      dim zfrnum as N=0
      dim lookone as N=0
      dim seeone as N
      dim cycle as N=0
      
      tbl = table.open("demographics")
      query.filter = ".T."
      query.order="familynumber"
      query.options=""
      xi = tbl.query_create()
      tbl.fetch_first()
      while .not. tbl.fetch_eof()
          cycle = cycle + 1
             if cycle = 20 then
                  goto haltme
             end if
         zfamnum = tbl.Familynumber
         zfrnum = tbl.Friendnumber
              ui_msg_box("REC","cyle="+cycle+" family="+zfamnum)
         lookone = zfamnum +.01
         numchk=convert_type(zfrnum,"C")
              if ".02" $ numchk then
      	   seeone=a5_get_records_in_query("demographics","Friendnumber ="+s_quote(lookone))
      	     if seeone = 0 then 
      	        ui_msg_box("SINGLE MOM",numchk+"  alone")
      [COLOR="Red"]	         zlastname = tbl.Lastname
      		zfirstname = tbl.Firstname
      		zmiddlename = tbl.Middlename
      		zcommonname = tbl.Commonname
      		zfullname = tbl.Fullname
      		zalphaname = tbl.Alphafullname
      		demo = table.open("demoprobe")
      		query.filter = ".t."
      		query.order=""
      		query.options=""
      		dxi = tbl.query_create()
      		demo.enter_begin()
      		demo.friendnumber = zfrnum
      		demo.familynumber = zfamnum
      		demo.lastname = zlastname
      		demo.firstname = zfirstname
      		demo.middlename = zmiddlename
      		demo.Commonname = zcommonname
      		demo.fullname = zfullname
      		demo.alphafullname = zalphaname
      		demo.enter_end(.t.)
      		dxi.drop()
      		demo.close()[/COLOR]
      	   end if
              end if
           tbl.fetch_next()
      end while
      haltme:
      xi.drop()
      tbl.close()
      
      ui_msg_box("wife alone","All done")
      end
      Mike W
      __________________________
      "I rebel in at least small things to express to the world that I have not completely surrendered"

      Comment


        #4
        possible solution ???

        Mike,

        query.filter = ".t."
        query.order=""
        query.options=""
        dxi = tbl.query_create()
        demo.enter_begin()
        If seeone is zero you're running a query against the demographics table, since you use the "tbl" pointer established for that table. Don't you mean this?

        Code:
        query.filter = ".t."
                 query.order=""
        	 query.options=""
        	 dxi = [COLOR="Red"]demo[/COLOR].query_create()
        	 demo.enter_begin()
        I think this is why you're losing the record pointer as you step through the demographics table.

        Having said that I don't see any reason you must open and close the second table each time seeone is zero. Open it once before the While Loop begins. Close it when your script ends.

        Furthermore, it's probably not necessary to run a query against the demoprobe table each time you want to enter a new record. I'm not seeing anything in the script which requires that any query be run against the demoprobe table.

        -- tom
        Last edited by Tom Cone Jr; 06-09-2006, 07:51 PM.

        Comment


          #5
          Yes! Wrong table pointer

          Tom,

          Your eyes have saved me once again. With that simpe change, it ran like a champ!

          As an official descendant of the Cherokee nation (my great, great grandmother was promiscuous) I do hereby grant you the honorary Cherokee title of Tom �Eagle Eye� Crone. May the Force continue with you.

          All kidding aside, I am a sapling (seasonal reference) in the A5 world and I appreciate your help a great deal. I �block� together codes that have worked in other places and then go from there. How aprepo your comments about needless query and closing the second table because I was wondering that myself, exactly! I figured it might not be necessary, but not hurt, and only inefficient, and after the script worked, I would start paring it down and discover, through trial, the essentials.

          You saved me a great deal of time and consternation. Thank you! Time to pare and learn�

          Mike W
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


            #6
            Using Debug or a second pair of eyes is the best way to solve a problem like this.

            However, if you really need to halt a long running script, see the "Halt Script" page in the help file.

            Comment

            Working...
            X