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

Script/Table Issue

  • Filter
  • Time
  • Show
Clear All
new posts

  • Script/Table Issue

    itn.zipITN Calc Update Samp.txt

    While Testing this set and scripts I have experienced some unusual errors that seem to come from out of the blue.
    I have heard the saying -" work on Sunday, Break down on Monday,"

    but in my case I worked and broke down on Sunday.

    I thought everything was working with stability over the past 2 days.
    After review of calculations made in Calculated fields in ITN.dbf, I revised some of the field rules using the Genie.
    I made the changes in ITN.set. I had some problems saving the changes but was able to correct any problems and save.

    I tried to recalc. field rules but the recalc command will not execute. It shows a progress bar at 0% and won't move.
    I used the exit command, exited A5 and then rebooted.
    I opened and checked the field rules in ITN.set and ITN.dbf but found no problems.

    I tried running the attached script, but I get a line 45 error stating that the result cannot fit a N field of that size.

    Further background - I did have to adjust a some field sizes on Friday night as data to be imported from1 record did not fit a specific field. I also made the correction in ITN where the data eventually would be stored as well. The program and scripts were still working fine 24 hours later. I tested all of the operations/routines in scripts last night and it worked fine.
    I revised about 6 Field Rules last night and the attached script started generating the line 45 error. None of the fields in this script were changed.

    Before I restore a back-up from yesterday and redo a few hours of work, does anyone have a suggestions on how to resolve this type of problem and what may be the cause?


    Bill W

  • #2
    Re: Script/Table Issue

    I am not quite clear on what the action that should be happening but there are a couple things I see. First, you open the table twice. Open it once with and get your list using <tbl>.records_get() instead. Also, I recommend using <tbl>.order() instead of <tbl>.query_create(). Less conflicts in my experience(). Acquire the count of the number of records in the list in a variable and use that variable in the for 1 to <var> so the script is not recalculating the number of lines in the list every pass. It looks like you have a conflict in the looping. You have a <tbl>.fetch_next within another loop. The table fetch gets the table to the last record and then what is supposed to happen?
    Mike W
    "I rebel in at least small things to express to the world that I have not completely surrendered"


    • #3
      Re: Script/Table Issue

      Thank you Mike W for the analysis and recommendations. After discovering a size of field problem, I emptied the tables, restored and then made the correction to the table structure and table rules. I have tested a few runs of the scripts and everything is working so far. My conclusion is that a structure change or field rule change caused some kind of corruption of data that caused the break.
      I will try to make to improvements recommended to the script.

      Thanks again

      Bil W


      • #4
        Re: Script/Table Issue

        Glad you got it to work,
        Just for accuracy, what I wrote should be :
        Open it once with and get your list using <tbl>.records_content_get() instead.
        Mike W
        "I rebel in at least small things to express to the world that I have not completely surrendered"