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

system->current_order

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

    system->current_order

    I am hoping some clever person knows the variable name that contains the string shown in the Order Builder as the order expression in the report writer.

    In the report writer, system-"current_order gives the order expression and it can be convenient to display this on a report.

    If a calculated field, say MyCalc, is used in the order expression, then the expression for MyCalc replaces the text string "MyCalc" when system-"current_order is printed, e.g. system-"current_order=a+b+c vs. system-"current_order=MyCalc.

    For my report, it is more understandable to print out "MyCalc", so I am trying to find a way.

    The only thing I thought of was to do processing in OnPrintInit, but system-"current_order is not available at that time.

    Bill.
    Tags: None
    #2
    RE: system->current_order

    Hello Bill,

    If you report is named "MyReport", a calculated field placed on the report with the expression:

    :MyReport.filter

    should give you the unparsed filter expression, ie:

    FieldName=var-"MyVarName

    whereas the system current_filter field returns the evaluated filter expression, ie:

    FieldName="value in the variable"

    Good seeing you at the conference. I say we have two conferences a year, one in Boston in the spring and one in Iowa in the fall.

    Jim

    Comment

      #3
      RE: system->current_order

      There is an Alpha function CURRENT_ORDER_EXPN(). The docs say:
      "To display the order expression that a report is based on, define a calculated field with this expression:
      Haven't tried it.

      Comment

        #4
        RE: system->current_order

        Thanks Jim. This is close...

        In the order expression builder the value for :Events.order displays correctly. If the report is run as a preview from dsign mode I get an error in the calculated field -
        :MyReport not found
        :MyReport.order

        If I save the report and run it, the report prints, but I get weird characters where the text is supposed to be.

        The current_order_expn() suggested by John is for table order, so your approach is probably what I need to figure out.

        Now if we want to experience Iowa at it's best, shouldn't we try to have a conference there in November to February?

        Bill.

        Comment

          #5
          RE: system->current_order

          While I am in the expression builder, the preview of cOrder = :MyReport.order shows the expression I want. However when printing cOrder field on the report I get an error that :MyReport.order is not found.

          Back in the calc field expression builder, F5 shows that the type is "F" for the cOrder calc field I defined. Anyone know what a type F is?

          If I play around a bit, it turns to a type= C. Then the report will print, but only if the report is saved first and preview is done from design mode. If design mode is closed, the error returns. Also the display object must be a text field, not a RTF.

          So I am close, but no banana yet.

          current_order_expn() just returned a blank field.

          Bill.

          Comment

            #6
            RE: system->current_order

            Bill, it may be a timing issue. I had some reports where I was setting the value of an RTF field(that existed only on the report) with a text variable established before I got there. The way I finally got it to work was to put xbasic-wait-for-idle in the onprintinit event.
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment

              #7
              RE: system->current_order

              Good try Martin. xbasic_wait_for_idle() seems to make the report preview work consistently from design mode (sometimes before it did not), but I still get the error when running report from control panel.

              Bill.

              Comment

                #8
                RE: system->current_order

                Hello Bill,

                Try this in the reports onPrintInit event:

                dim global vOrder as c
                vRep = this.this
                vOrder = vRep.order

                Now add the vOrder variable onto the report. Works for me.

                Good luck,
                Jim

                Comment

                  #9
                  RE: system->current_order

                  Selwyn says that :report.order is not a valid run-time property, so I have asked if this could be made available in the future.

                  To recap, if your order expression is "calc-"MyCalc + field1" and calc-"MyCalc = "a+b", system-"current_order gives "a+b+field1", but there appears no way to get 'calc-"MyCalc +field1" outside of design mode.

                  Bill.

                  Comment

                    #10
                    RE: system->current_order

                    Hello Bill,

                    Try this; remove any onPrintInit event code, and place a global variable named vOrder on the report. Then call the report with this code:

                    dim global vOrder as c

                    r = report.Load_Low("Customer List")
                    vOrder = r.order
                    r.close()

                    report.preview("Customer List")

                    This appears to work every time for me. We are creating a little overhead here, but I hope not too much.

                    Jim

                    Comment

                      #11
                      RE: system->current_order

                      Jim is the intrepid Alphaholic as usual.

                      Comment

                      Previous template Next
                      Working...
                      X