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

Any ideas

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

    Any ideas

    I'm sure there is a very easy solution to this but I'm not sure how to do it. How would I get the name of the current index to either display on a form or be able to use the current index's name in a calculated expression? Any help would be greatly appreciated.

    #2
    RE: Any ideas

    "tbl".index_primary_get()
    Syntax:
    "Index> = "Tbl".index_primary_get()
    Description:
    Returns an object pointer, ("Index") that references the primary index or query
    list of the table referenced by "Tbl". The primary index is the index that is
    currently controlling the order of the records in the table.
    Example:
    'Display the name of the primary index in the Trace window.
    '----------------------------------------------------------
    tbl = table.current()
    index_pointer = tbl.index_primary_get()
    index_name = index_pointer.name_get()
    trace.writeln("The name of the primary index is: "+index_name)
    See Also:
    "tbl".index_primary_put()
    There can be only one.

    Comment


      #3
      RE: Any ideas

      Thanks Stan. I learned something new! Appreciate the help.

      Comment


        #4
        RE: Any ideas

        You're welcome. All I did was cut and paste from the pdf. I just happened to remember that I had seen it.
        There can be only one.

        Comment


          #5
          RE: Any ideas


          ...and from there, to get it printed on the form or report?

          And to which event would this script be attached?

          Comment


            #6
            RE: Any ideas

            index_name = index_pointer.name_get()

            The variable named index_name now contains the name of the current index. Create a field that refers to this variable to have it display or print.

            If you want this to display on a form the event question is problematic. Suppose you have a button on the form which allows "index setting". You would want to have this code on the button after the code to set the index, before the code to refresh the parent form. If you don't have such a button, but the user has access to the normal menu, I would suggest attaching the code (plus the refresh) to the ontimer event. I can't think of another way to ensure that the variable is updated if the user changes indexes via menu.

            For a report you could set the variable in the onprintinit event to ensure currency.
            There can be only one.

            Comment


              #7
              RE: Any ideas


              "Create a field that refers to this variable to have it display or print."

              Details, please?

              Comment


                #8
                RE: Any ideas

                At some level, probably most conveniently form level maybe table level, declare this index_name to be a global variable (character).

                From the drop drag list you will then have the variable available to drop onto the form. In a report you might need to created a calculated field = var->index_name if you use the form level declaration. Then you can place the calculated field on your report.
                There can be only one.

                Comment


                  #9
                  RE: Any ideas

                  Testing seems to indicate that the easiest place to declare the variable is at the table level, edit structure, table menu, global variables, global, index_name, character, "".

                  This is then available to forms and reports based on the table.

                  tbl = table.current()
                  index_pointer = tbl.index_primary_get()
                  index_name = index_pointer.name_get()
                  :Sm_Testing:Index_Name.Refresh()

                  placed in the oninit event for the form "Sm_testing" displays the name of the current index tag (at the time the form is first displayed) in a field created by dragging the index_name field from the drag-drop list (variables section of the list). Other events would need the same code under the conditions described earlier.
                  There can be only one.

                  Comment


                    #10
                    RE: Any ideas


                    thank you!

                    Comment

                    Working...
                    X