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 messages

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

    error messages

    I have an application that I distribute with A5V10.5 run-time.

    One of my customer reports that he gets errors when running a couple scripts. See attached screen shots.
    It suddenly started happening on a working system with no changes made to it.

    The two scripts shown are essentially to select a text file, rename it and then import it into an existing table.
    The operation has been working flawlessly for many years (with previous versions of A5 of course)
    It's been used with A5V10.5 for about a year now without issue.

    The error messages refer to a table that I do not use in my app but they look like temporary tables created by A5. The field names are correct for my tables.

    Only this customer gets these error messages, nobody else. He has also uninstalled and reinstalled A5 and my app.

    He has even tried uninstalling my app and installing an earlier version of my app plus A5V8 runtime.

    Any ideas what could cause this to happen to him ?

    Thanks.
    Attached Files

    #2
    Re: error messages

    It is hard to get this one from the description. Can you give the name of the table he is supposed to be accessing at this point.

    Not knowing and first sight, it seems the table may have been renamed(truncated) to the 8 and 3 dos convention, so alpha is trying to resolve and found this temp table?? Is it possible that some crash of the system has occured? Possibly posting the script(s) could give more clues?

    Others may have seen this before, I have not. Possibly more information could better help us to help you??
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


      #3
      Re: error messages

      Both screen shots reference a "...temp_table". Is this table being created or auto-filled by earlier steps in the sequence the user is running? If so, you may have a timing problem here. Remember, scripts that call operations do not wait for those operations to complete before moving on and executing later statements in the script. Is this customer's machine setup significantly different than your other customers? i.e. does it have resources that would cause it to run faster or slower than other machines?

      -- tom

      Comment


        #4
        Re: error messages

        The table names referenced are the same as my destination tables names except "_Temp_Table" is added to my table name.
        My table name is Captured_Data. The name in the error message is Captured_Data_Temp_Table.
        My Table was SKU_Master. The error message table was SKU_Master_Temp_Table

        As far as I can tell from what my customer told me, nothing has changed on his laptop.

        There is part of me that thinks it's hardware related. Crazy things can happen to a computer if the power supply is failing. They usually just get weaker instead of dying all together.

        These particular scripts are used by many of my customers on a very frequent basis and I've never had to put a "Wait for Idle" in the script.

        Comment


          #5
          Re: error messages

          Ok, John.

          If memory serves imports to an existing table are (behind the scenes) handled in two steps. Import to temp tables, then append from the temp tables to the final destination table. Your scripts may be failing because the temp tables have not yet been created and filled... on this particular machine.

          Comment


            #6
            Re: error messages

            I guess I'll throw in a couple Wait-for-Idle commands and see if it fixes it for him.

            I'll let you know how it turns out.

            Comment


              #7
              Re: error messages

              John, if my guess is right "wait for idle" won't help.

              Suggest you break the import op down into two distinct operations. Using a temp table you create. Then run them separately by hand. Does the problem go away on the offending machine? If so, then wrap both operations in user defined functions and run them back to back in a new script. The script will pause while each udf runs to completion.

              Comment


                #8
                Re: error messages

                I'll give it a go. I'll let you know what happens. Thanks.

                Comment

                Working...
                X