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 - hassle

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

    report - hassle

    have a set
    parent - CUSTOMER
    ----- child1 - TRANSACTIONS
    -------------grandchild - PAYMENTS
    ----- child2 - INSUREDS

    this is a medicaid/insurance/etc report printing out on the HFCA-1500 form

    when i put transactions in "details" it is printing a record for each child(transactions) and for the grandchild, too (payments) - in other words is printing more than once for each transaction

    this is my first experience with "grandchildren"

    there are no groups

    have tried "blank duplicates" unsuccessfully

    although i can remove the grandchild with an extra set especially for the report - is there a standard way people deal with this issue?

    thanks
    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 - hassle

    Martin:

    I don't think you need to make a set just for the report. Your way of avoiding duplicate composite records is probably via grouping levels. You may also need subreports.

    I assume the customer is linked 1:N to transactions and to insureds. Also transaction is linked 1:N to payments.

    If so, you most likely will have to group on customer. Then make subreports for transactions and insureds. The transaction subreport will require a grouping on transaction so you see payments by transaction.

    (I think subreports accept grouping levels.)

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: report - hassle

      Hi Martin:

      I would guess that your grandchild is linked similar to your child. If you link your grandchild specific to the a certain instance of the child that should clear it up. I would link them by say date or some other filtering method.

      Also on the detail section of the report you can specify a record order and a filter expression.

      Good luck

      Dan
      Dan

      Dan Blank builds Databases
      Skype: danblank

      Comment


        #4
        RE: report - hassle

        Bill's right. You have to use groups. The detail section will give you one grandchild record per detail. Grouping is what allows you to get multiple 'details' on one report.

        Some reports only need summary info and not all the details. In those cases, you would take the 'detail' section right out of your report.

        Comment


          #5
          RE: report - hassle

          okay - got it to work
          parent and child1 and child2 are linked via patientid, whereas transactions are linked to payments (grandchild) via transaction number

          what i did was remove the detail section and put in a group that breaks on transaction number, using set ordering.

          the report is filtered on patientid=var->cnum, so that it only prints one report. I got it working fine, now.

          I don't need any of the payments info for this form. It took a lottttttttt of changes to get everything to print exactly where its supposed to print on the form, but it looks mossssst excellently

          thank's for the help.
          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


            #6
            RE: report - hassle

            heyyyyyyyyyyy dan
            looking forward to seeing you again saturday at out user's group meeting - missed the last few due to personal difficulties, namely that I came home from work about two months ago and my place was burned down. what a major hassel. i lost virtually everything. fortunately almost all of my cd's(software) were inside a briefcase and were still good. so was able to reinstall alpha, etc.

            took forever to get everything back the way i like it
            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

            Working...
            X