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

More report problems!

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

    More report problems!

    With Tom's considerable help I have now managed to get some fields in some rows to split in the right place and display on the report over two or more rows. Great!

    However...

    All the fields on the report need to be "boxed". In other words I need to have every row of data separated by a graphic line (no problem there, I just draw a line across the bottom of the fields in the detail section of the report designer) and every column split by a vertical line. How do I draw a line vertically which will adjust to the height of the row? That is, most report rows will be one character high, but some rows will be two or three characters high, often due to the height of only one field in that row. I only seem able to get the line to extend the height of one character?

    Oh, and one other thing. When a field is "inside" an RTF, how does one change the font?

    I'm so close! Please help!

    #2
    RE: More report problems!



    Martin Wolff wrote:
    -------------------------------
    Oh, and one other thing. When a field is "inside" an RTF, how does one change the font?

    Highlight the field and use the text toolbar to change it's text properties.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      RE: More report problems!

      Thanks, Al,

      The TextToolbar works perfectly for all fields OTHER than RTFs (it's fine for headings, etc. As soon as I highlight an RTF field, the Text Toolbar "greys out" and becomes unuseable.

      ???

      Comment


        #4
        RE: More report problems!

        Instead of highlighting the RTF object, can you highlight the field object inside of it?

        -- tom

        Comment


          #5
          RE: More report problems!

          No, Tom, this is what I've been trying to do but, once "inside" an RTF the original field seems inaccessible.

          Martin.

          Comment


            #6
            RE: More report problems!

            Martin,

            I'm beginning to think you need to do your report with another tool. Maybe a strong word processor or something like Crystal Reports. Your requirements are approach a desktop publishing level that may be beyond what Alpha Five can do.

            One last idea. Put each field in its own RTF object, and set the border properties of that object to create the box you need.

            -- tom

            Comment


              #7
              RE: More report problems!

              Tom,

              That works, sort of. Problem is that the border doesn't print at all around an empty field (I'll see what happens if I put some non-printing character into an empty field).

              Also, across a row where most fields are one character high, but one field is two characters high, the border only prints half way down on the single-height fields.

              Ah, well. No thoughts about the font-changing-in-RTFs querie, I suppose?

              Martin.
              PS. Working at the weekend? What's wrong with us?

              Comment


                #8
                RE: More report problems!

                Martin,
                Double click on the RTF field. Then left click and highlight the text that needs a font change. You can use the text box that opens to change the font of you can select properties from the right-click menu and change the font from there.

                Comment


                  #9
                  RE: More report problems!

                  Martin

                  Can you post a small example of what you are doing so we can look at it and not play 20 questions?
                  Al Buchholz
                  Bookwood Systems, LTD
                  Weekly QReportBuilder Webinars Thursday 1 pm CST

                  Occam's Razor - KISS
                  Normalize till it hurts - De-normalize till it works.
                  Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                  When we triage a problem it is much easier to read sample systems than to read a mind.
                  "Make it as simple as possible, but not simpler."
                  Albert Einstein

                  http://www.iadn.com/images/media/iadn_member.png

                  Comment


                    #10
                    RE: More report problems!

                    Ohlen,

                    thanks for the step by step. I was sure one could select the field and manipulate its properties, even after dropping it on the RTF. Guess I didn't think to tell Martin how to do it....

                    -- tom

                    Comment


                      #11
                      RE: More report problems!

                      Thanks Ohlen, didn't realise you could/had to highlight the text of the fieldname. So I can now change the font!

                      In xbasic I've added a chr(13) to the end of each single-character-high field for records in the temporary print file (don't add them to your "live" database) where there is at least one two-character-high field. That makes the border of the RTF the correct height on all fields.

                      Now all I have to do is work out what to do for empty fields, where, currently, no brder prints at all. All ideas gratefully received - if I solve it, I'll let you know!

                      Martin.

                      Comment


                        #12
                        Report - Border doesn't print when field is blank

                        "Now all I have to do is work out what to do for empty fields, where, currently, no border prints at all. All ideas gratefully received - if I solve it, I'll let you know!

                        Martin.
                        "

                        Martin, have you ever solved this problem?

                        I'm faced with this same issue using A5V7. I guess it doesn't matter which version you're using.

                        If the field is blank, no border.

                        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


                          #13
                          Ron

                          Have you tried a conditional object?
                          Al Buchholz
                          Bookwood Systems, LTD
                          Weekly QReportBuilder Webinars Thursday 1 pm CST

                          Occam's Razor - KISS
                          Normalize till it hurts - De-normalize till it works.
                          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                          When we triage a problem it is much easier to read sample systems than to read a mind.
                          "Make it as simple as possible, but not simpler."
                          Albert Einstein

                          http://www.iadn.com/images/media/iadn_member.png

                          Comment


                            #14
                            Yes Ron, I've just looked at that app., and it seems that I got around it by making the fields RTFs and, in the Properties for the field (Setup tab) ticking Allow growth when printing and Allow shrink when printing (and creating a border of course). I thought I had put dummy (non-printing) characters into empty fields but it doesn't look as if I did.

                            Anyway, it's been working OK for a couple of years now. Hope this helps.

                            Comment


                              #15
                              I've been busy with other things, sorry for the late thank you.

                              While the conditional object would work, it will be far too tedious for this project.

                              I'll give Martin's suggestion a try.

                              Thanks,

                              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