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 with word wrap bug?

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

    Report with word wrap bug?

    I'm having a problem with a report.

    There is one grouping level and a detail section.

    One of the fields in the detail section is a calculated field. This field can hold up to six full names. The TRIM function has been used to keep the data in the field as short as possible.

    Due to space limitations, the field on the report has been shortened and word wrapping has been selected. The only way I can get the word wrapping to work is to make the field on the report two rows high.

    I have selected "SHRINK WHEN PRINTING" at the end of the region and in the properties of the field.

    My problem is that as long as the field is blank, the shrink when printing works "OK". However; if there is only one name in the calculated field, then the report prints with both lines present even though the second line is blank.

    This results in an ugly looking report and wastes a lot of paper.

    I've used this technique many times in Alpha 4. What's wrong with Alpha 5? Is this a bug?

    Ron
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

    #2
    RE: Report with word wrap bug?

    You're right, this isn't working the same as in A4, because DOS and Windows don't work the same.

    Try this: Put a Rich Text Field on the report where your calc field was, and then put the calc field in it. Make the RTF as tall as one line (assuming you have other fields for this line). This will expand and contract as necessary.

    Comment


      #3
      RE: Report with word wrap bug?

      I tried your suggestion. Unless I'm doing something wrong, I still can't get this to work right.

      You said: "You're right, this isn't working the same as in A4, because DOS and Windows don't work the same."

      What do you mean by this statement?

      What works in DOS won't work in windows? All I did was select the settings that Alpha Software furnished. They worked in Alpha 4, I would think that they would work in Alpha 5. Why else would Alpha software provide these choices?

      Ron
      Alpha 5 Version 11
      AA Build 2999, Build 4269, Current Build
      DBF's and MySql
      Desktop, Web on the Desktop and WEB

      Ron Anusiewicz

      Comment


        #4
        RE: Report with word wrap bug?

        Ron,

        "I still can't get this to work right."

        What happens? Does the field fail to expand as desired? I believe RTF fields have an "allow expand on print" checkbox.

        Be alert to the fact that sometimes report options may conflict with one another. On occasion I have had to remove options and add them back one at a time to isolate the conflict.

        In adapting your A4 instincts to Alpha 5 you are experiencing something most of us have been through and it can be frustrating because the sense of mastery one had in A4 vanishes in the initial stages of migrating to A5. I can only encourage you to persevere and ask questions. The reward is that when you get into it the windows environment is more powerful and empowering.

        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: Report with word wrap bug?

          You asked what I mean about DOS and Windows working differently. In the case of Allow Shrink, this is meant to shrink a field to zero height IF the field evaluates to blank. The example I suggested using an RTF should give you what you want. Make sure you have check the Allow Shrink box, and ALSO make sure the field as placed on the form is VERY short. In other words, put the calc field in the RTF, and then click on the middle of the bottom of the field where you see the little black square, and drag the bottom of the field upward as far as you can.

          As Bill H. pointed out, moving from A4 to A5 can be frustrating, because you expect things to be the same. In many cases, they simply aren't (I sometimes think that having learned A4 is a disadvantage when trying to learn A5). I think we all went through a period of discomfort (loathing? tearing hear out?) during the learning curve. But it is DEFINITELY worth it. So, stick with it. We're all here to help.

          Comment


            #6
            RE: Report with word wrap bug?

            Hi Bill,

            I guess if didn't explain the problem correctly.

            I have a calculated that contains anywhere from none up to six full names. Having all six names on one line would make the field too long for the report.

            I selected word wrap so that if the field contained three names or less, they would be on the first line. Any names in excess of three would wrap down to the second line.

            My problem is that even if there is only one name, the report prints the second line as a blank line. I don't want that to happen. The only time I want the second line to print is when there is a name in the second line.

            The only reason I mention Alpha 4 is that Alpha 4 could do this. I'm sure you can do this with Alpha 5. Right? I just haven't been able to figure out how to do this.

            Ron
            Alpha 5 Version 11
            AA Build 2999, Build 4269, Current Build
            DBF's and MySql
            Desktop, Web on the Desktop and WEB

            Ron Anusiewicz

            Comment


              #7
              RE: Report with word wrap bug?

              Ron,

              A couple of thoughts:

              1. "I have a calculated that contains anywhere from none up to six full names...My problem is that even if there is only one name, the report prints the second line as a blank line."

              Perhaps it is taking a second line because of spaces at the end. Use the trim function to your calculation to remove trailing blanks.

              2. Do the six names come from six separate fields? If so, forget the calculated and place the fields directly in the rich text object separated by ctrl-enter. The field will size itself automatically.

              Bill
              Bill Hanigsberg

              Comment


                #8
                RE: Report with word wrap bug?

                Another possibility is to split you name calc field into two calc fields, fist three names in the first field - second three names in the seciond field. Then there could be up tp three names but the second field could be completely blank, and behave the way you want.

                Comment


                  #9
                  RE: Report with word wrap bug?

                  Thanks John,

                  I figured it out myself, but my solution was what you suggested. The first field has four names and the second has two names.

                  Mickey mouse, but it works.

                  This trimmed a 33 page report down to 28.

                  Thanks again,

                  Ron
                  Alpha 5 Version 11
                  AA Build 2999, Build 4269, Current Build
                  DBF's and MySql
                  Desktop, Web on the Desktop and WEB

                  Ron Anusiewicz

                  Comment


                    #10
                    RE: Report with word wrap bug?

                    Ron,
                    Glad you got it working. I'm not sure I'd look at breaking up a calculated field into two elements, one for each report line as Mickey Mousing it. I'd consider it a design improvement.
                    John

                    Comment


                      #11
                      RE: Report with word wrap bug?

                      Well, I wasn't satisfied with spliting up the calculated field. After testing, I came up with some instances where the results weren't right.

                      I tried the other suggestion of placing the calculated field into a rich text field. I don't know why I couldn't get it to work the first time, but I did manage to get it to work now, with one exception.

                      The exception is that in one example, instead of a full name, I have a +1 to signify a person. This +1 just happens to be at the end of the line and is wrapped to the next line. For some reason, It is overwritten by the next line.

                      I'm sorry, but I do believe that this is a bug.

                      Thank you to all who responded.

                      Ron
                      Alpha 5 Version 11
                      AA Build 2999, Build 4269, Current Build
                      DBF's and MySql
                      Desktop, Web on the Desktop and WEB

                      Ron Anusiewicz

                      Comment


                        #12
                        RE: Report with word wrap bug?

                        Ron,

                        Is it possible Alpha Five is somehow interpreting +1 as an addition operation in your report? Do you get the same results if you use 11?

                        -- tom

                        Comment


                          #13
                          RE: Report with word wrap bug?

                          Hi Tom,

                          I changed the +1 to 11 and the word wrapping worked properly. So then I changed 11 to +11 and it worked properly. Next I changed +11 back to +1 and now it seems to be working properly. I deleted the +1 and ran the report and then entered the +1 and the report worked properly.

                          I must tell you that I'm a little concerned at Alpha 5's reliability and constancy. I happened to find this error strictly by accident. I was proof reading the report and noticed the omission. The only reason I found it was
                          the name Doug had a dot above the letter o.

                          Now I'm questioning Alpha 5's ability to generate accurate reports.

                          Ron
                          Alpha 5 Version 11
                          AA Build 2999, Build 4269, Current Build
                          DBF's and MySql
                          Desktop, Web on the Desktop and WEB

                          Ron Anusiewicz

                          Comment

                          Working...
                          X