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

Refreshing "Current_Order" field

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

    Refreshing "Current_Order" field

    I placed the system filed "Current_Order" on my form to show what the current table index order is. After I use the select index/query menu item, I want the current_order field on the form to be refreshed to display the new index order. I'm looking at Refresh_fields() and "form".resynch(), but I haven't gotten it to work yet. Can anyone provide the answer? Thanks.

    -Dave

    #2
    RE: Refreshing

    objectname.refresh()

    where objectname is the name revealed by examining the current_order field on the form, probably will be current_order unless you have changed it.
    There can be only one.

    Comment


      #3
      RE: Refreshing

      Stan -

      OK, yes I left the system field name as "Current_Order". Now, where do I place the "current_order.refresh() function? I have a button on the form that pulls down the index selector. I want the current_order to automatically change once the index is chosen. Right now, it only changes if I click in the current.order field. I tried putting this command in the "onpush" action, but it does not refresh the field. I tried on depart as well - still no automatic field update. Any ideas?

      -Dave

      Comment


        #4
        RE: Refreshing

        I assume you are using action scripting to "pulls down the index selector". After this action add another, xbasic, inline xbasic, with the current_order.refresh() as the code.
        There can be only one.

        Comment


          #5
          RE: Refreshing

          Stan -

          I've tried this, it's not working. I converted the action script to Xbasic, and here's what I have for the Onpush event for the button that's uesed to select index:

          'Date Created: 21-Sep-2005 09:59:21 AM
          'Last Updated: 21-Sep-2005 11:22:48 AM
          'Created By : wilsodab
          'Updated By : wilsodab
          'Display standard Index/Query Select dialog in current form.
          topparent.IndexSetDialog()
          current_order.refresh()

          Is there something missing perhaps?

          -Dave

          Comment


            #6
            RE: Refreshing

            I started to reply that

            topparent.IndexSetDialog()

            should be

            topparent.IndexSet()

            and it should, but something is not working right. I'll experiment and get back to you.

            .IndexSetDialog(), according to the documentation, is used in the context of a form pointer variable.....

            dim frm as P

            frm = form.view("Customer Information")

            frm.indexsetdialog()
            There can be only one.

            Comment


              #7
              RE: Refreshing

              OK, thanks, let me know if you find an answer. I think 6.0 has a few bugs still. It appears that 7.0 Beta has fixed some that I run into - such as the Export to Excel not working most of the time. I haven't tried this refresh piece on 7.0 Beta yet, but I can test it tonight to see if it works differently on 7.0 Beta. I'm looking at 7.0 now, and it looks really good. The only problem I will have is that at my day job, I don't have admin rights on my box, and I can't even install 7.0 because of that. I've approached Alpha about that, but I don't know if they will be able to offer a workaround or not.

              Anyway, thanks for looking at it & let me know if you find any solition.

              -Dave

              Comment


                #8
                RE: Refreshing

                Perplexing but at least I know what is happening.

                The script
                topparent.IndexSet()
                current_order.refresh()

                does not pause after the first line. So the second line is executed before the index set takes place, effectively displaying the order before it is chosen.

                Now for a fix/workaround..................
                There can be only one.

                Comment


                  #9
                  RE: Refreshing

                  Stan -

                  OK, your analysis makes sense. I will try the application that has this code on my V7.0 machine tonight to see if it works as we think it should. If it does, then I guess its a bug in 6.0?

                  I'll report back on my 7.0 findings ASAP.

                  -Dave

                  Comment


                    #10
                    RE: Refreshing

                    Stan -

                    Just as an FYI, it does the same thing in version 7.0 Beta.

                    Comment


                      #11
                      RE: Refreshing

                      The .INDEX_SET() method returns a logical value. Test for the return value before running the next statement.

                      Comment


                        #12
                        RE: Refreshing

                        A better strategy might be to use .INDEX_PRIMARY_PUT() and wait for the return value.

                        Comment


                          #13
                          RE: Refreshing

                          After reading the documentation I don't see how to do that, but that's not surprising. I was able to mangle the example code for .index_set() and come up with this

                          t = table.current()
                          'count the number of indexes/queries
                          count = 1
                          while (t.index_name_get(count) != "")
                          count = count + 1
                          end while

                          dim list[count] as C 'I think this line needs to come
                          'after the variable is initialized, not before
                          'create an array with the index names
                          list[1] = ""Record number order""
                          for I = 2 to count
                          list[I] = t.index_name_get(I-1)
                          next i
                          index_name = ui_get_list_array("Choose an index", 1, "list")
                          if index_name = ""Record number order""
                          parentform.index_set("")
                          else
                          parentform.index_set(index_name)
                          end if
                          current_order.refresh()
                          There can be only one.

                          Comment


                            #14
                            RE: Refreshing

                            Stan -

                            I actually found a very simple way to do it:

                            1. Put the current_order.refresh()command in the form's ONTIMER event

                            2. Set the ONTIMER interval in the form properties to a value greater than 0.

                            This does exactly what I wanted - just change the value of the current order field on the form automatically to what the currently chosen index is. Very simple, I used this before for an on-form clock, but could not recall where to set the timer interval. But I finally cound it.

                            Anyway, thanks, I will also look at the other methods you and Ed mention so I know how to do it that way too.

                            -Dave

                            Comment

                            Working...
                            X