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: Invalid Table Handle????

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

    Error: Invalid Table Handle????

    Heres the script i wrote to do my monthly imports from the import table to the usecost table. This is also imcuded in a text flie in the zip file with the 2 tables in question.

    'Date Created: 25-Jun-2004 05:15:19 PM
    'Last Updated: 25-Jun-2004 05:15:19 PM
    'Created By : Administrator
    'Updated By : Administrator
    dim quotefield as c
    dim usagefield as c
    dim costfield as c
    dim master as p

    on error goto Error_Handler

    monthselect="Aug"

    IF monthselect="Jan" THEN
    quotefield="Jan_Cost"
    usagefield="Jan_Usage"
    Costfield="Jan_Cost"
    ELSE
    IF monthselect="Feb" THEN
    quotefield="Feb_Cost"
    usagefield="Feb_Usage"
    Costfield="Feb_Cost"
    ELSE
    IF monthselect="Mar" THEN
    quotefield="Mar_Cost"
    usagefield="Mar_Usage"
    Costfield="Mar_Cost"
    ELSE
    IF monthselect="Apr" THEN
    quotefield="Apr_Cost"
    usagefield="Apr_Usage"
    Costfield="Apr_Cost"
    ELSE
    IF monthselect="May" THEN
    quotefield="May_Cost"
    usagefield="May_Usage"
    Costfield="May_Cost"
    ELSE
    IF monthselect="Jun" THEN
    quotefield="Jun_Cost"
    usagefield="Jun_Usage"
    Costfield="Jun_Cost"
    ELSE
    IF monthselect="July" THEN
    quotefield="July_Cost"
    usagefield="July_Usage"
    Costfield="July_Cost"
    ELSE
    IF monthselect="Aug" THEN
    quotefield="Aug__Cost"
    usagefield="Aug__Usage"
    Costfield="Aug__Cost"
    ELSE
    IF monthselect="Sept" THEN
    quotefield="Sept_Cost"
    usagefield="Sept_Usage"
    Costfield="Sept_Cost"
    ELSE
    IF monthselect="Oct" THEN
    quotefield="Oct_Cost"
    usagefield="Oct_Usage"
    Costfield="Oct_Cost"
    ELSE
    IF monthselect="Nov" THEN
    quotefield="Nov_Cost"
    usagefield="Nov_Usage"
    Costfield="Nov_Cost"
    ELSE
    IF monthselect="Dec" THEN
    quotefield="Dec_Cost"
    usagefield="Dec_Usage"
    Costfield="Dec_Cost"
    ELSE
    END IF
    END IF
    END IF
    END IF
    END IF
    END IF
    END IF
    END IF
    END IF
    END IF
    END IF
    END IF
    master=table.open("usecost")
    post.t_db = "import"
    post.m_key = "CUSTOMER_ID-DISTRIBUTED_ITEM_CODE-DISTRIBUTOR"
    post.t_key = "str(CUSTOMER_N,10,0)-ITEMNUMBER-DISTRIBUTO"
    post.m_filter = ""
    post.t_filter = ""
    post.m_count = 3
    post.m_field1 = quotefield
    post.m_exp1 = "@Import-"Month_Quote"
    post.m_field2 = usagefield
    post.m_exp2 = "@Import-"Month_Use"
    post.m_field3 = costfield
    post.m_exp3 = "@Import-"Month_Cost"
    post.t_count = 0

    master.post()
    master.close()'If the Operation is run from within a Form or Browse, then refresh the window
    if is_object(topparent.this) then
    if topparent.Class() = "form" .or. topparent.class() = "browse" then
    topparent.Refresh_layout()
    end if
    end if

    error_handler:
    ui_msg_box("Error","The following error occured. " + crlf(1)+error_text_get(error_code_get())+crlf() \
    + "On Line: "+error_line_number_get())
    master.close()
    stop

    i get the blue bars at the bottom like it's working... the number 250 comes up down there and then i start to get my errors. Take a look please and see what i missed.. i know it's something dumb on my side... just need a fresh set of eyes and maybe a brain transplant!

    Thanks in advance

    #2
    RE: Error: Invalid Table Handle????

    First, a couple questions. Since you have an error handler, is that showing any error? If it is, what error are you getting? If the post works until record 250, that would possibly indicate a problem with that record, not necessarily a problem with the post. Without the tables and data to test, it is only a quess.

    A suggestion. While it would no bearing on your problem, I would suggst using "select, case" statements rather that a series of "if" statements. You will find it runs quicker and gives less trouble in complex expressions. My rule of thumb is normally to use if only when there are 2 possibilities, true or false. If there are more than 2 possibilities use select, case.

    Jerry

    Comment


      #3
      RE: Error: Invalid Table Handle????

      Bah, i forgot to atach the zip file i made, it has everything you need to test this.

      I'll take your advise about the case statement as i agree it's probably a better way to do it.

      As for the error handler it was giving me an error at the master.post line.. with a title of invalid table handle, hense the subject =0)

      thanks again and heres the files this time.

      Comment


        #4
        RE: Error: Invalid Table Handle????

        Charles

        There were a number of problems with the files you posted. You did not include the data dicationary files (ddd, ddm, ddx) so all of the long name references were lost. Also the memo file (fpt) file for "usecost" was missing.

        After making the corrections, I found two problems. First, the field names in "usecost" are inconsistent in format. Some fields used single underline in the name "_", and some use double underlines "__". Double underlines have caused problems in other situations and should be avoided. This inconsistency carried over to the script, where some field names used single underlines and some used double. These names did not seem to match the actual names in the table. If the field name in your post doesn't match the actual field name in the table, the post will fail.

        After changing the field names to single underlines, and simplifying the script to set the field variable names, the post runs smoothly.

        The second problem was in the script itself. There was no END statement before the error handler code, therefore the error handler came up every time the script ran with an error 0.

        Attached is a zipped copy of the database after making corrections. The new script that runs the post is named "testscript"

        Jerry

        Comment

        Working...
        X