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

Multiple print problem

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

    Multiple print problem

    In our customer menu, we have a serach that pulls up our customer's billing address, shipping address, contacts, and the last message that we have sent them. It is set up with the same code that is used in the sample invoice customer to bring up the corresponding browse (contacts). What I am now finding is that when I have more than one contact, I get a duplication of the memo field. Meaning if there are five names in the browse, there will be five copies of the memo. I was wondering if anyone could help me untangle this printing problem. (I have written very few codes on my own that worked.)

    Thanks

    Jeff
    Tags: None
    #2
    RE: Multiple print problem

    This is a clarification. THe code used is the multistate button.

    Also the report that is printed will only fit as many copies of the memo field as will fit on the one page with the appropriate headers and footers.

    Jeff

    Comment

      #3
      RE: Multiple print problem

      Ran in to this and had to redesign our sets (tested and confirmed thatit could be replicated in the sample databases sent with A5). If you have more than 1 one-to-many links (on the same level) for some reason this happens. Don't know if this fits your case or not. If it does, you have to decide which one-to-many you can live without. We had to eliminate an embedded historical browse in order to get duplicate invoices to work from our main set because of this (the invoices printed multiple detail lines and the onRowDoubleClick() failed as well). Removing one of the one-to-manies fixed the problem. Trying a few dozen alternate set structures didn't. Too bad. The historical browse helped a lot.

      Comment

        #4
        RE: Multiple print problem

        I only have one link that is one-to-many. THere is only two tables involved with this set. I cannot think of how this can get confused. to make things easier in getting the name (contact) correct on the top of the fax, I switched to a field on the parent table. I had it figured out that if you highlighted the name in the browse it would use that name. I thought this would make it easier. I just want the contacts there for reference, not for any part of the actual printing of the fax form.

        Any other thoughts?

        Jeff

        Comment

          #5
          RE: Multiple print problem

          In a set with a 1:N link Alpha Five creates a 'virtual record' for each combination of parent and child records in the design. This is used when displaying information from the set on a form, or when printing a report based on the set.

          For instance in a simple set with one parent table and one child table, linked one-to-many this is what they would look like:

          Parent table contains:
          Smith
          Child table contains:
          Sally
          John
          Tom

          The 'virtual records' are:

          Smith Sally
          Smith John
          Smith Tom

          As you can see, the field value from the one parent record is repeated for each virtual record. These 'virtual' records are sometimes called 'composite' records.
          I think your memo field is probably found in your parent table, and is repeating because of the 1:N link.

          Check out the related discussions on p. 156 in the User Guide and p. 59 through 65 in the Xbasic Reference Manual.

          - tom

          Comment

            #6
            RE: Multiple print problem

            I have checked out the pages you recommended and frankly, am confused on where to go using this information. I realize now that I need to come up with a way to limit the field to a single record of the multiple variations, (Tom, John,...) Is there an easy way to print to the Smith family without creating a letter for each member?

            Jeff

            Comment

              #7
              RE: Multiple print problem

              Actually there are more than one.

              I often leave the set 'as is', but add a group break to the report, based on the linking field between the parent table and the child table.

              Then I put the fields from the parent table in the 'group header', and the fields from the child table in the 'group details'. Summaries, totals and counts I put in the 'group footer'. Grand totals covering all 'groups' in the report I put in the 'report footer'.

              You will find that if your report is based on a one-to-many set and you include fields from the parent table in the 'details' section of your report you see the values repeat over and over. By putting them in the group header you only see them once. Even though they are present 'virtually' in the set, since you don't put them in the details section, you never see them after the header prints.

              Hope this makes sense. Even if it doesn't, I recommend you experiment along these lines. I'm sure you'll be able to figure it out.

              -- tom

              Comment

              Previous template Next
              Working...
              X