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

invalid key length

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

    invalid key length

    I have been using the following script for 3 years every business day w/o any issues, until today:

    tbl3=table.open("Tbl_AssignProjects")
    tbl4=table.open("Tbl_AssignProjects")

    query.description = "AllProj"
    query.order = "" 'This is a FIELD, NOT an Index!
    query.filter = "DATE = Copy_From_Date"
    query.options = "" 'D for Descending
    tbl3.query_create()

    tbl3.fetch_first()
    while .not. tbl3.fetch_eof()
    vBlob3 = tbl3.record_data_get()

    tbl4.enter_begin()
    tbl4.record_data_set(vBlob3)
    tbl4.DATE = Copy_To_Date
    tbl4.LINK = Left(tbl3.LINK,4) + cdate(Copy_To_Date)
    tbl4.enter_end(.t.)
    tbl3.fetch_next()
    end while

    tbl3.close()
    tbl4.close()

    Now I'm getting "invalid key length" error msg at the line: tbl4.enter_end(.t.) upon the first record entry.

    What does "invalid key length" specifically refer to?

    Peter
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com



    #2
    RE: invalid key length

    Peter

    Did something change on your computer that should not have affected this? If a process works for 3 years and then stops working, something else has changed.

    Did you load the latest patch from Alpha? or a patch from Microsoft?

    Have you considering changing the tbl4(or3).date to another name that is not a conflict with a reserved word? And describes what date is being stored.

    Where did Copy_To_Date get dimmed?

    Is tbl4.Link a key?

    What does debug show is the value that is to be placed in that field?
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      RE: invalid key length

      Peter, I don't follow the logic of your script. Hard to see how the script ever ends since tbl3 and tbl4 are pointers to the same table. As you step through the table you enter new record one at a time, and continue til ... ?

      -- tom

      Comment


        #4
        RE: invalid key length

        Right. Query tbl3 for yesterday's (or Friday's, if it's a Monday) records. Write them to tbl4 (yep, same table). I use this method to copy records within tables. Always worked until today. I thought it might be a bad record, but records seem to be ok. Did install latest patch today - after that problem showed. Installed old patch - problem still there. It's a puzzlement.

        ?
        Peter
        AlphaBase Solutions, LLC

        [email protected]
        https://www.alphabasesolutions.com


        Comment


          #5
          RE: invalid key length

          Did something change on your computer that should not have affected this? If a process works for 3 years and then stops working, something else has changed.

          Did you load the latest patch from Alpha? or a patch from Microsoft?

          Installed latest A5 patch today. Problem then appeared. Re-installed old patch. Problem still there.

          Have you considering changing the tbl4(or3).date to another name that is not a conflict with a reserved word? And describes what date is being stored.

          Again, I have been using this exact script for 3 years.

          Where did Copy_To_Date get dimmed?

          ok, it's there, just didn't post that part.

          Is tbl4.Link a key?

          Yes it is.

          What does debug show is the value that is to be placed in that field?

          well, the debugger won't show you the blob contents, but otherwise it appears the record is properly fetched. it's the save command that bugs out.

          PG
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            RE: invalid key length

            I take it back. It does work in 1488/1046. So it appears to be a bug 1494/1049. Will get it to Selwyn this w/e.

            PG
            Peter
            AlphaBase Solutions, LLC

            [email protected]
            https://www.alphabasesolutions.com


            Comment


              #7
              RE: invalid key length



              Peter Greulich wrote:
              -------------------------------
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein

              http://www.iadn.com/images/media/iadn_member.png

              Comment


                #8
                RE: invalid key length

                I'm surprised this worked:

                query.filter = "DATE = Copy_From_Date"

                If copy_from_date is dimmed locally, the query filter would have no context...

                it should be

                query.filter = "DATE = "+copy_from_date
                or maybe
                query.filter = "DATE = "+quote(copy_from_date)
                if it is a character var
                Aaron Brown
                Alpha Software Development Team

                Comment


                  #9
                  RE: invalid key length

                  Aaron,

                  It is a shared var. I did not post that part of the script.

                  Peter
                  Peter
                  AlphaBase Solutions, LLC

                  [email protected]
                  https://www.alphabasesolutions.com


                  Comment


                    #10
                    RE: invalid key length

                    Problem resolved:

                    There is no bug, per se'.

                    However, for some reason an innocent comment line (that's probably been there for two years) that was located just before the tbl4.enter_end(.t.) caused the script to fail in the latest patch 1494-1049. That comment line was not a problem in any previous patch.

                    Wierd, but true...
                    Peter
                    AlphaBase Solutions, LLC

                    [email protected]
                    https://www.alphabasesolutions.com


                    Comment


                      #11
                      RE: invalid key length

                      Peter

                      Thanks for letting us know.

                      That type of error is tough to find. What pointed you in that direction?

                      Probably another good reason to post actual databases to the message board for others to look at. Sometimes the solution is not based on what we think it should be.
                      Al Buchholz
                      Bookwood Systems, LTD
                      Weekly QReportBuilder Webinars Thursday 1 pm CST

                      Occam's Razor - KISS
                      Normalize till it hurts - De-normalize till it works.
                      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                      When we triage a problem it is much easier to read sample systems than to read a mind.
                      "Make it as simple as possible, but not simpler."
                      Albert Einstein

                      http://www.iadn.com/images/media/iadn_member.png

                      Comment


                        #12
                        RE: invalid key length

                        What pointed you in that direction?

                        I was preparing a scaled down version for Selwyn and eliminated all the rems, etc. and then it worked. So I just backtracked it and voila!
                        Peter
                        AlphaBase Solutions, LLC

                        [email protected]
                        https://www.alphabasesolutions.com


                        Comment


                          #13
                          RE: invalid key length

                          Hi Peter,

                          Did you ever test your old script to see if it compiled properly in the new build. I have had occasional problems after installing a patch. A script would fail so I would open it in design mode to see what was wrong. Like your case, it would be something which had been working for a long time so I'm asking what gives.

                          I then press F4 to test the compile and it reports an error and points to a line number. Removing the comment removes the error. Put the comment back again and it works fine.

                          The only common factor I found was a blank space after the code and before the comment (before the apostrophe). Sometimes even a blank space after the code caused a problem even if not followed by a comment.

                          I report all of this without much confidence that it is the whole story or even true. But I thought it best to share my experience since it seems so similar to your own.

                          Bill
                          Bill Hanigsberg

                          Comment


                            #14
                            RE: invalid key length

                            Did you ever test your old script to see if it compiled properly in the new build.

                            Yes, Bill. No error was reported.
                            The error may well have been "a blank space" or perhaps some invisible character. I could test it against a backup copy, but it's not worth the effort at this point in time.

                            Peter
                            Peter
                            AlphaBase Solutions, LLC

                            [email protected]
                            https://www.alphabasesolutions.com


                            Comment


                              #15
                              RE: invalid key length

                              Bill,
                              When debugging, there is no "whole story", just some knowledge,your own experiences, a logical approach, and if you're fortunate enough, the advantage of learning from other's experiences. I have erased and retyped the exact same line in a problem script, and the script magically worked. And, by the way, some of these scripts compiled correctly.
                              John

                              Comment

                              Working...
                              X