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

Perpetual process in autoexec script fails

  • Filter
  • Time
  • Show
Clear All
new posts

  • Perpetual process in autoexec script fails

    I would like Alpha to append one table to another table every 15 minutes. The records in the table to be appended are changed regularly and have to be appended to the original table.

    I tried this script on an autoexec script:
    goto re_run
    but Alpha appears to hang, as the autoexec script never finishes running.
    How can I accomplish the "perpetual updating"?

    Jay Talbott
    Jay Talbott
    Lexington, KY

  • #2
    Re: Perpetual process in autoexec script fails


    First of all, the autoexec code is run once, when the application is opened - in your case it is running in a loop - I take it that you had to invoke CTRL-ALT-DEL to stop the scipt from running.

    Just based on the little that you have given, if you have a main menu form that is always open, you could set the timer on that form for 15 minutes and then put your code in the forms OnTimer event.

    My question is how were you doing it before you decided to use the autoexec script?

    The one problem I forsee is that the append could take place while someone is adding a record to the table. The append operation would lock the master table. (The table that the records are being appended to) Is that file in use at any time.

    You may want to look at "appending" or writing it to the table in an onSave event from the form that the data entry is being made. This would be done every time you save the record and would not need a "Perpetual append".

    Is the whole record being appended to the new file or partial fields? Is there a reason for waiting 15 minutes? I take it you are only appending new records from the transaction table to the master table.

    When I need to append records to another table, I usually write them at the time the record is saved and not use an append - using tbl.enter_begin() and tbl.enter_end().

    Tom Baker
    Last edited by Tbaker; 04-18-2010, 06:36 PM.


    • #3
      Re: Perpetual process in autoexec script fails

      Thanks for your response. I am going to use the main menu idea.

      The complete situation is like this:

      Client has a web and desktop application which are related. Nightly, files from the desktop app are FTP'd automatically up to the web server. In rare instances, the clients wants to update the web files immediately (within a few minutes) and not wait for the nightly update. So since no data entry is taking place on the web server, the onTimer event of the main menu is a great way to handle it.

      Thanks again.
      Jay Talbott
      Lexington, KY


      • #4
        Re: Perpetual process in autoexec script fails


        The OnTimer event will fire every 15 minutes for as long as the main menu form (the one that you will be using) is open. If that form is open 24/7 the OnTimer event will try to append records to the master continuously every 15 minutes.

        How to you determine what records to append. I would think that you would have a logical field that is true to append that record and after appending is set to false so it will be appended just one time.



        • #5
          Re: Perpetual process in autoexec script fails


          The append operation allows "Unique, replace existing" which will prevent multiple records. Each night the "temporary asap" file will be zapped and the next day, it can be refilled with new "asap" names.

          Your onTimes suggestion with a main_menu will work perfectly. Thanks again.
          Jay Talbott
          Lexington, KY


          • #6
            Re: Perpetual process in autoexec script fails


            Thanks for the reply.



            • #7
              Re: Perpetual process in autoexec script fails


              The sleep() command does just that - it puts Alpha to sleep. And, just like when you go to sleep, it won't do anything else while it's sleeping. In your example it puts it to sleep for 900 seconds or 15 minutes. Of course, to a user it appears to be hung up but it really isn't; it's just doing what you told it to do.

              You also might want to check out the Script_schedule() function. This could be used to schedule a script to repeat every 15 minutes without needing a form open and, with a little more work, it could be set to schedule the script to run only during particular times of day/night.