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

report order question

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

    report order question

    I have a set:

    contracts
    -----customers(1 to 1 1st match) [linked to contracts]
    ----------phones(1 to many)[linked to customers]

    the report has in details, e.g.:

    contracts->custid, customers->lastname, subreport(phones)

    the report prints perfectly, the filter being contracts amountdue > 0

    but it will not take an order expression

    in design, I can go to the order, and select [customers->lastname-customers->firstname] for the order expression, and it will "evaluate" correctly, but when I save and print, it prints by record number order

    then I go back to the orderexpression, and I note that the order expression will not save - it gets removed

    if I remove the subreport, the orderexpression will save.

    have tried many iterations, even changing the set to:
    contracts
    -----customers
    -----phones
    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

    #2
    RE: report order question

    converted to V5, same problems

    I also made a set:

    customers
    -----phones[1 to many]
    -----contracts[1 to 1]

    customers
    -----phones[1 to many]
    -----contracts[1 to many]

    still won't work
    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


      #3
      RE: report order question

      Martin, I think maybe the difficulty is your desired sort sequence uses fields in one table, and your filter expression uses fields in a different one. The report layout cannot alter the linkage specs defined in the set.

      I say maybe cause I don't use subreports, and it's possible the presence of the subreport object itself is limiting your sort sequence options.

      I could take a look at it this weekend, if you send me the database, or post it here. -- tom

      Comment


        #4
        RE: report order question

        Tom, I think I have figured it out. In general, if you use a subreport in details, like the following

        set=
        customers
        -----phones(1 to many)

        details line in report=

        custid---fullname---[subreport(phone--phone type)]

        the above will print perfectly, but I cannot get the report to accept and save and use an ordering on parent(lastname-firstname)

        BUT

        if I add a group break, break on custid, and order the group on lastname-firstname and put customer info in the group header and phones in details, (but not as a subreport,) it will order correctly.

        The issue seems to be the use of subreports.

        The same thing is true in 4.5 and 5.0

        Anyway, I found a successful workaround, as usual. Alpha is so flexible, that so far, (a little grumbling notwithstanding,) I have never had a problem that I couldn't find someway around.
        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


          #5
          RE: report order question

          Martin, I'm glad you have it figured out. Your solution is how I generally approach things. I don't use subreports unless I have two 1:N child tables linked to the same primary table, and need to display data side by side. (As illustrated in the User Guide). Fortunately, this doesn't happen often.

          -- tom

          Comment

          Working...
          X