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

ui_get_list_array

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

    ui_get_list_array

    Hello
    I am trying to create a list array of a field value for the purpose of filtering records on a form. The code I have written returns the correct values to the trace window, but does not populate the array
    Code is as follows
    tbl = table.current() 'bankouts.dbf
    tbl.fetch_first()
    count = tbl.records_get()
    FOR i = 1 TO count
    vSearch_for = (dtoc(tbl.date)+" "+tbl.name)
    trace.writeln(vSearch_for) 'test result correctly
    tbl.fetch_next()
    choice = ui_get_list_array("Choose a Bankout",1, "vSearch_for")
    IF choice = "" THEN
    END
    END IF
    'code here
    NEXT i

    I know I can embed a browse of the records and filter by date but the form is very full already and I dont want the end user to type in a value to search by.

    Help me Mister Wizard


    Nick

    #2
    RE: ui_get_list_array

    Nick,

    You need to dim the array first and then assign the values. Here's an example:
    dim namearray(15) as C
    dim i as n
    i=1
    tbl=table.open("menus",file_ro_shared)
    tbl.index_primary_put("field1")
    tbl.fetch_first()
    while .not.tbl.fetch_EOF()
    namearray(i)=tbl.username
    i=i+1
    tbl.fetch_next()
    end while
    tbl.close()
    thisws=ui_get_list_array("WORKSTATION NAME",1,"namearray")

    In my case I know that 15 is enough, you may need more or less.
    Pat Bremkamp
    MindKicks Consulting

    Comment


      #3
      RE: ui_get_list_array

      Hello Pat

      Thanks for your help

      Nick

      Comment


        #4
        RE: ui_get_list_array

        Hi Pat

        Well I tried and now I get "array index out of range"
        Here are the changes based on your suggestion
        dim vSearch_for (30) AS C
        dim i AS N
        i = 1
        tbl = table.current()
        tbl.index_primary_put("Search_by")
        tbl.fetch_first()
        While .not. tbl.fetch_EOF()
        vSearch_for(i) = dtoc(tbl.date)
        i = i+1
        tbl.fetch_next()
        End While
        choice = ui_get_list_array("Choose Bankout",1,"vSearch_for")
        IF choice = "" THEN
        END
        'code here
        END IF

        If you have any more suggestions they would be appreciated.

        thanks
        Nick

        Comment


          #5
          RE: ui_get_list_array

          Nick,
          In the script you posted, it looks like there is an extra space in your array dim statement:
          is
          dim vSearch_for (30) AS C
          should be
          dim vSearch_for(30) AS C

          That could be the problem.
          Pat Bremkamp
          MindKicks Consulting

          Comment


            #6
            RE: ui_get_list_array

            Sorry about the typo but it is written without the space. The xbasic manual displays this error if the variable is declared incorrectly. It's not also I checked the table to insure there are no busted records or incorrect date values.

            Nick

            Comment


              #7
              RE: ui_get_list_array

              "array index out of range" could also mean that in your
              vSearch_for(i) = dtoc(tbl.date), "i" passed the original dim statement value of 30, I think.

              Did the error return a line number? If it wasn't line number 1, then it was probably later in the script.
              Are you sure 30 is enough?

              Try using the debugger and seeing if the script bombs on the dim statement or only when it is processing the assignment loop.
              There can be only one.

              Comment


                #8
                RE: ui_get_list_array

                You might try changing:
                dim vSearch_for (30) AS C
                dim i AS N
                i = 1
                tbl = table.current()
                tbl.index_primary_put("Search_by")

                to:
                dim i AS N
                i = 1
                tbl = table.current()
                tbl.index_primary_put("Search_by")
                records = tb1.records_get()
                dim vSearch_for(records) AS C

                Comment


                  #9
                  RE: ui_get_list_array



                  Nick:
                  Let Alpha count how many records exist in the lookup database. I think
                  it's safe to say that you should probably not limit the dimension of the array
                  since the lookup database can conceivably grow beyond the size of the
                  array. This may not be exactly what you need, but it should get you
                  going...
                  tbl = table.current()
                  tbl.index_primary_put("Search_by")
                  count = tbl.records_get()

                  dim vSearch_for(count) AS C
                  dim i AS N

                  i = 1

                  tbl.fetch_first()

                  While .not. tbl.fetch_EOF()
                  vSearch_for(i) = dtoc(tbl.date)
                  i = i+1
                  tbl.fetch_next()
                  End While

                  choice = ui_get_list_array("Choose Bankout",1,"vSearch_for")
                  IF choice = "" THEN
                  END
                  end if
                  'place code here
                  end
                  Craig

                  Comment


                    #10
                    RE: ui_get_list_array

                    Thanks Everyone
                    We will give them a try.

                    Nick

                    Comment


                      #11
                      RE: ui_get_list_array

                      Craig,

                      Just a small suggestion. Set count = count +1. For some reason I have seen array out of bounds errors pop up when the array is dimensioned to the exact number of possible records. This has happened on an irregular basis, but just enough to cause me to pull out the remaining gray hair.

                      Jerry

                      Comment


                        #12
                        RE: ui_get_list_array

                        Hello once again

                        Craig your change to read the entire table works perfect. thanks again to all of you

                        Nick

                        Comment


                          #13
                          RE: ui_get_list_array

                          Jerry:

                          Your point is well taken, but probably falls short of resolving why you have the array-out-of-bounds errors.

                          The reason for your error is likely that between when you get a record count, and when you load the array, some other user has added a record.

                          In Nick's case, his script will allow only a fraction of a second for this to occur. Other scripts may have a larger window within which records can be added to the lookup, disrupting the array.

                          So I guess it should be count = (count) + (maximum number of users)!

                          Interesting point, Jerry!

                          Good food for thought...

                          Craig

                          Comment

                          Working...
                          X