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

How to �NOT� use Fields in a Report

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

    How to �NOT� use Fields in a Report

    I have 8 fields (pgrm1 thru Pgrm8) There is a corresponding numerical field for each Pgrm field. I will always use at least 1 Pgrm field and the corresponding numerical field but up to as many as all 8 fields could be used. The goal is to only display the Pgrm fields, along with the corresponding numerical field, on the report �IF� the Pgrm field is not Null or IOW, if it contains data.

    This is how it would work.

    During data entry, the user will enter a Pgrm in one or more of the Pgrm fields and also enter a numerical value in the corresponding numerical field. (A drop down will be used to choose the Pgrm value).

    Data entry example:
    Pgrm1 Num1 Pgrm2 Num2 Pgrm3 Num3 Pgrm4 Num4
    Pgrm5 Num5 Pgrm6 Num6 Pgrm7 Num7 Pgrm8 Num8

    Say only Pgrm1 and Pgrm2 and the corresponding Num1 and Num2 fields contain a value. On the report, I only want these fields to appear. I do not want the other fields to appear on the report.

    Report Example:
    Pgrm1 Num1 Pgrm2 Num2

    Now, the $64 million dollar question. How can this be done?
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    Re: How to �NOT� use Fields in a Report

    3 words

    conditional objects

    or

    html reporting
    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: How to �NOT� use Fields in a Report

      Hi Al,

      I figured this would have to be contained in a conditional object. The example in the documentation is for a use on a form and has little application to a report. The HTML in reports does not have anything to do with conditions other than conditions about formatting appearance. I'll keep searching but that's all I found in the documentation using 'Reports', 'HTML' and 'Conditional Objects'. My next method will be to search Alpha using Google.
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment


        #4
        Re: How to �NOT� use Fields in a Report

        Originally posted by forskare View Post
        Hi Al,

        I figured this would have to be contained in a conditional object. The example in the documentation is for a use on a form and has little application to a report. The HTML in reports does not have anything to do with conditions other than conditions about formatting appearance. I'll keep searching but that's all I found in the documentation using 'Reports', 'HTML' and 'Conditional Objects'. My next method will be to search Alpha using Google.

        Conditional objects work great in reports. No difference in use of a form or a report.

        HTML reporting is a little tricker. Build the HTML from an xbasic function that looks at the fields and decides what to show.
        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


          #5
          Re: How to �NOT� use Fields in a Report

          I found the Conditional Object info for reports using Google. Now it's time to experiment and see what happens.

          Thanks for the directional approach.
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment

          Working...
          X