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
Devcon 2020 Goes Virtual! LEARN MORE >

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 key length

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    ERROR: Invalid key length

    Ok guys, (and girls)

    I keep getting the error message listed in the title.

    Here's the senerio: I have a table "documents". In this table I have 2 fields. "Date" and "Document". All I want to do is to sort this table by either "Date or "Document". I typed the following into my script and the Interactive Editor and got the error both ways! What's the deal?

    Interactive session:
    Code:
     
dim tbl as P
tbl = table.open("documents")

i = tbl.order("Date")
 
?i.type_get() 
= 6
 
i = tbl.order("Document")
ERROR: Invalid key length
    It only fails on "Document". Is there a max key length for the order() method?
    Tags: None
    #2
    Re: ERROR: Invalid key length

    Is there a max key length for the order()
    Yes.
    I don't remember the exact number though.
    The shorter the better.

    Comment

      #3
      Re: ERROR: Invalid key length

      Click on the first thread listed at the bottom of this message under similar threads.
      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

        #4
        Re: ERROR: Invalid key length

        Originally posted by G Gabriel View Post
        Yes.
        I don't remember the exact number though.
        The shorter the better.
        Al, Thanks! I'll do that.

        I'm taking it that by key length, Alpha means the actual length of the values in the field?

        I was able to work around this by creating a calculated field that stores a substring of the field I wanted to order by.

        ADDED: Alpha supports using partial fields for sorting. I am sorting a table of filenames. The filename is stored with it's path. ex: c:\windows\somefile.xxx so I used a regex to get the filename. :)

        ADDED MORE: By the way, the regex to get a filename out of it's fully-qualified path is:
        regex_merge(string as C,"[[:alnum:]]+\.[[:alnum:]]+","","AI")


        I'm sure it's in the documentation, but, since I'm here. =D How do I do reverse sort using the order() method?
        Last edited by Jeff@Listbrokers; 11-14-2006, 06:23 PM. Reason: ADDED was an after though.

        Comment

          #5
          Re: ERROR: Invalid key length

          max key length = 240 characters (for the "Search Forum Challenged"...) Thanks, Al!

          Comment

            #6
            Re: ERROR: Invalid key length

            Originally posted by Jeff@Listbrokers View Post
            max key length = 240 characters (for the "Search Forum Challenged"...) Thanks, Al!
            Code:
            dim tbl as P
tbl = table.open("documents")

i = tbl.order("Date")
            - ascending

            Code:
            dim tbl as P
tbl = table.open("documents")

i = tbl.order("invert(Date)")
            - descending
            There can be only one.

            Comment

              #7
              Re: ERROR: Invalid key length

              Jeff, use the Invert() function to reverse the sort sequence.
              Code:
              tbl.order("invert(Document)")
              Assuming the field width of the Document field isn't larger than the max key width.

              Comment

                #8
                Re: ERROR: Invalid key length

                Originally posted by Jeff@Listbrokers View Post

                ADDED MORE: By the way, the regex to get a filename out of it's fully-qualified path is:
                regex_merge(string as C,"[[:alnum:]]+\.[[:alnum:]]+","","AI")

                While you can use the regex, you can also use the Alpha function....

                FILE.FILENAME_PARSE()

                Code:
                dim t as P
dim filename as C
t = table.open("customer")
  filename = t.filename_get()
  filename -> "K:\PROGRAM FILES\A5V4\TEMPLATES\DATABASES\INVOICE\CUSTOMER.DBF"

 file.filename_parse(filename,"n") -> "CUSTOMER"
  file.filename_parse(filename,"e") -> ".DBF"
  file.filename_parse(filename,"ne") -> "CUSTOMER.DBF"
                I'd be interested in a comparison in the execution speed. Have you used profile_begin() and profile_end() to measure execution speed of code?
                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

                  #9
                  Re: ERROR: Invalid key length

                  Thanks Stan and Tom. That's exactly what I need! :)

                  Originally posted by Al Buchholz View Post
                  While you can use the regex, you can also use the Alpha function....

                  FILE.FILENAME_PARSE()

                  Code:
                  dim t as P
dim filename as C
t = table.open("customer")
  filename = t.filename_get()
  filename -> "K:\PROGRAM FILES\A5V4\TEMPLATES\DATABASES\INVOICE\CUSTOMER.DBF"
 
 file.filename_parse(filename,"n") -> "CUSTOMER"
  file.filename_parse(filename,"e") -> ".DBF"
  file.filename_parse(filename,"ne") -> "CUSTOMER.DBF"
                  Al, Thanks for the solution. That's exactly what I need too... :)

                  I'd be interested in a comparison in the execution speed. Have you used profile_begin() and profile_end() to measure execution speed of code?
                  I haven't used the profile_() functions,yet. I didn't even know they existed! :) I'll definitely give them a work out.

                  If I'm not mistaken, I believe the regex is supposed to be faster. I'll post my results.

                  Comment

                    #10
                    Re: ERROR: Invalid key length

                    When I'm using order("invert(table)") is there anyway to see if my table is sort has already been inverted? something similar to <index>.order_get() ?

                    I want the table to be sorted ascending first... then I want it to toggle afterwords.

                    Is there's a better way to do what I'm trying to do?

                    I have a browse and when a user double clicks on a particular column I want the table to be sorted on that column.

                    Comment

                      #11
                      Re: ERROR: Invalid key length

                      bump
                      Last edited by Jeff@Listbrokers; 11-15-2006, 02:06 PM. Reason: accidental

                      Comment

                        #12
                        Re: ERROR: Invalid key length

                        Hey Al,

                        F.Y.I. (and anyone else that reads this): I was just reading in the documentation about those profiler functions. They're named PROFILER_BEGIN() and PROFILER_END(). Anywho, I'm about to test them out and will be posting the results for ya' in a sec. Thanks again!
                        Last edited by Jeff@Listbrokers; 11-15-2006, 01:16 PM.

                        Comment

                          #13
                          Re: ERROR: Invalid key length

                          I'd be interested in a comparison in the execution speed. Have you used profile_begin() and profile_end() to measure execution speed of code?
                          Hey Al, I can't get profiler_() to print anything to a trace or a file... so I guess no results today. :(

                          Comment

                            #14
                            Re: ERROR: Invalid key length

                            Are you opening the trace window from the menu? view - trace window - profiler tab?


                            Or providing a fully qualified file name to profiler_end()? (oops - left the r out before...)

                            ie profiler_end("c:\mytrace")


                            Interestingly enough, I just did a test on my system with a copy of Alpha that has been open for awhile and I've bee doing some development work on. So I decided to use profiler_* to get some results of the code I just wrote.

                            I couldn't get profiler to write to the trace window or to a file.

                            Exited Alpha - Restarted Alpha - opened the same db - ran the same script - got results in the trace window - changed code to write to a file - got results there too.



                            Please try it again after an A5 restart.
                            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

                              #15
                              Re: ERROR: Invalid key length

                              Originally posted by Al Buchholz View Post
                              Are you opening the trace window from the menu? view - trace window - profiler tab?


                              Or providing a fully qualified file name to profiler_end()? (oops - left the r out before...)

                              ie profiler_end("c:\mytrace")
                              I went to view - trace window... I don't have a profiler tab. I have "User",'Errors',"hook errors","c:\dlgstack.log","ViewEvent". I used a fully qualified address. The file never got created. I even used debug to verify the script executed the profiler statements... looks like it is. I'll restart Alpha and see what happens. I have restarted it several times today so I don't think that'll fix it, but we'll see. :)

                              Comment

                              Previous template Next
                              Working...
                              X