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

Blank Fields in a Report

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

    Blank Fields in a Report

    I am designing a report for a chorale group so members can verify or update their information at the upcoming first rehearsal of the new season.

    For most members, not all of the fields in the table are populated. i.e. Most do not have a second e-mail, and that field will be blank on the report.

    I want a border around each field, whether blank or not, so the member knows where to put in data. For example, they want to list a cell phone that wasn't previously provided.

    If I insert a field in the report and format it with a border, only populated fields show up on the report. In other words, a blank field does not show up as an empty box. (Attached "Member Update0.pdf")


    To work around this I reformatted all the fields with no border. I then inserted a frame with a border for each field position and put the field inside the frame. As you can see in the attached file (Member Update 1.pdf) the results weren't any better. The populated fields show up properly, while blank fields so not. For all fields except "Email (Secondary)" the frame is only slightly taller than the field. (Frame = .2" field = .187") "Email (Secondary)" frame = .3" and the field is positioned at the top of the frame and slightly to the right of the left frame.

    So the question is: How do I get a bordered box for each position of the report, whether the corresponding field is populated?

    TIA
    "There comes a point in every project where it becomes necessary to shoot the engineers and begin production."

    #2
    Re: Blank Fields in a Report

    Adding a frame here shows up when no data....so something else is going on....a sample is the only way for me! :)

    A conditional object may work as well if a frame turns out to not...
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


      #3
      Re: Blank Fields in a Report

      Thanks for the reply Mike.

      I went back and played with it a bit and found I could get the bordered frame to show up as long as the field borders were completely inside the frame. However, the size of the displayed frame changed depending on whether the field is populated or not. See the e-mail fields on the attached file. (Members Update 2.pdf)

      Having said that....

      This was on kind of a short deadline, so I tried something else. I got the results I wanted by doing this as a Letter rather than a Report, and it came out as I wanted. (Members Update.pdf)

      When I get more time I will play with the conditional object as you suggest.

      I am confused as to why the report module and the letter module would work so differently.

      --------
      "There comes a point in every project where it becomes necessary to shoot the engineers and begin production."
      "There comes a point in every project where it becomes necessary to shoot the engineers and begin production."

      Comment


        #4
        Re: Blank Fields in a Report

        Nice that you have figured out a solution (and posted it here!). You will find the availability of various ways to do pretty much the same thing to be present in most of Alpha, but this can also confuse a developer at the same time as to which way it should be tackled.

        I believe the letter module is basically a RTF field and so it doesn't surprise me that they may act a bit different....I don't use it as a rule as the report writer can do most/all that it can do and more.

        Your differences in frame size....check your frame properties and uncheck both the can shrink and allow growth checkboxes and see if that prevents the size change.
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #5
          Re: Blank Fields in a Report

          The confusion continues, but the problem seems to be solved. In Frame Properties, "Allow to Grow" is checked by default. I assumed (Yea, yea, I know...:) ) that was what I wanted so I left it. As you suggested, I unchecked it and the formatting is just as I wanted (and consistent) for both the populated and empty fields. I even moved the fields to the upper left corner of the frame so it is touching both the top and left border and it is still o.k. In the attached file, "Members Update 3.pdf," you can see the results. All the frames are the sizes I formatted.

          The confusion comes from, "Why does 'Allow to grow' cause the frame to shrink?"

          I realize these formatting quirks (and other fine tuning) of reports, letters, etc aren't the core of the program, but most of these tweaks are poorly documented. I guess I am so spoiled by the ease of just about everything in A5 I forget that every now and then I actually have to think.

          But it is still beats the "good ol' days" of A4 V 1.1 when you had to enter printer codes into the report for each formatting element you wanted. (And that was still easier than Paradox!)

          Anyway, thanks for your help, Mike.
          "There comes a point in every project where it becomes necessary to shoot the engineers and begin production."

          Comment

          Working...
          X