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

Bad Object Handle

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

    Bad Object Handle

    Have read other threads on this topic but they don't really point me in the right direction.

    I have a form based on a table in which its first (indexed) field is an auto-increment numeric one. A form opened in new entry mode displays that field in a Numeric Type-in-field with an object name FIELD1 and other date, character and numeric fields.

    When the form is loaded there is an error message 'Bad object handle' which I think must refer to FIELD1 although I can't track down what the error is or what triggers it. (In A5 Help each reference to a handle seems to indicate that it is not used in A5 any more).

    Once the error message box is closed the form works exactly how it should, including the expression in the FIELD1 property which supplements the autoincrement - I don't think this has anything to do with the error problem.

    How can I find out which object it refers to without deleting each one to test whether there is still an error on the form load?

    Mike

    #2
    RE: Bad Object Handle

    ""How can I find out which object it refers to""
    When you get the error, open the Trace window, it will outline which and what.
    Gabe

    Comment


      #3
      RE: Bad Object Handle

      Gabe - The Trace window didn't really help me track the error. Details were:-

      View Event:-
      FRM_RESYNCH_ENGINE to Form for Deals database 5
      ======Session 4======================
      Deals recno = 19 order=Deal_Num;.T. key=:0

      HookError
      addin.variables().a5_error_show(Bad object handle) : *INTERMEDIATE_0000002b.a5_error_show method not found.

      Any further ideas please? Mike

      Comment


        #4
        RE: Bad Object Handle

        Can anyone help me sort out this problem please? Is it an A5 bug? Mike Vance.

        Comment


          #5
          RE: Bad Object Handle

          Mike, is the name of the field in your table "field1"?
          typically that is a field name assigned in an import.

          When you say you are "supplimenting" the autoincrement - that may be happening at onfetch - autoincrements are very fickle
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            RE: Bad Object Handle

            Mike,

            A useful start in any troubleshooting session is to check the behavior of the table using its default form. Right click the table name or icon in the control panel, choose open default form, enter and edit a few dummy records. Does it behave correctly? if so that's a good sign the field rules are ok and that your trouble lies in the custom data entry form you built. if the trouble shows up using the default form that's a good sign the trouble lies in the expressions you're using in field rules.

            -- tom

            Comment


              #7
              RE: Bad Object Handle

              Martin - yes my object name is Field1 - provided automatically by Alpha Five when I put the object on my form.

              The autoincrement does 'kick in' when the form loads but my code seems to work after that.

              Comment


                #8
                RE: Bad Object Handle

                Tom - the default table is fine i.e. the autoincrement works by adding 1 each time. I do appreciate the problem lies within my form but the hook error (see below) does not make sense to me. I think it is a bug because it refers to a show-method error. What is that error all about?

                HookError
                addin.variables().a5_error_show(Bad object handle) : *INTERMEDIATE_0000002b.a5_error_show method not found.

                Comment


                  #9
                  RE: Bad Object Handle

                  As Martin has previously suggested, the code you're using to "supplement" the value supplied by the auto increment field rule bears close examination. I would start there by deleting that code from the form to see if that eliminates the error.

                  If the autoinc field rule does not meet your needs, instead of using it and then modifying the resulting value a cleaner (easier to debug) approach would be to use a custom autotinc script, entirely abandoning the field rule. Examples are to be found in the Code Archive.

                  -- tom

                  Comment


                    #10
                    RE: Bad Object Handle

                    Thanks Tom - I'll try your suggestions and report back after I've had another go. Mike

                    Comment


                      #11
                      RE: Bad Object Handle

                      Mike,

                      I am getting the same Bad Object Handle error with a form I have designed and have been using for over a year. It does an auto-increment on the field invoice number. The form works fine. The table it references is part of a set. Whenever I close a form associated with the set I get the alert "bad object handle". I, too, have tried to troubleshoot this using the trace window. The info is too vague for me to pinpoint. Did you ever resolve the problem? Deb

                      Comment


                        #12
                        RE: Bad Object Handle

                        Deb - I didn't manage to solve the problem as I would have wished.

                        What I did was 'strip' out all the code to leave the auto-increment field alone. Then, each month the table was cleared of all records and the auto increment started again at 0 for the first new record of the new month.

                        Not ideal but I couldn't get it to start at a number I used in a variable and gave up! Mike

                        Comment


                          #13
                          RE: Bad Object Handle

                          Mike/Deb:
                          I think I am pretty close to solving your mystery.
                          couple questions:
                          Did you design this form in A5V5 ? or
                          Did you copy it or import it from another database?
                          Gabe

                          Comment


                            #14
                            RE: Bad Object Handle

                            Gabe - My form was designed in V6.

                            I think I know what you have in mind. Quite a few calculated fields for dates and other field types which work perfectly in v5 do not work if the database is run in v6 - they should do. The only way round that problem appears to be to start a new form completely!

                            Thanks for your interest. Mike

                            Comment


                              #15
                              RE: Bad Object Handle

                              Mike:
                              No, that's not what I have in mind.

                              My understanding is that you were trying to get autoincrement to start from a number you used in a variable. What was the expression or script you used to do that?

                              Gabe

                              Comment

                              Working...
                              X