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

Conditional Report compared to many reports??

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

    Conditional Report compared to many reports??

    Hi,

    Just a general question really but involves a major decision for what I do next.

    When given a choice of using conditional objects on a report so that one report can be used instead of 9 (maybe 16) different separate reports which way should I go. Seemingly you would think that one report is much less work than creating 9 or 16 but in this case all that is needed to create the varying reports is to basically copy the previous one and add or remove various fields and such. Whereas I have been finding creating conditional objects has its own problems such as keeping all the objects in line, and at times having them corrupt and having to delete and recreate to make them work again....and then there is the problem of bleed-through under certain conditions --and what is incredible is the bleed-through actually is printed!

    So is there ANY reason to use conditional objects on a report instead of simply duplicating a report and doing the slight modification it would require??

    I cannot see one so would like another opinion just to make sure I am thinking correctly in this.


    Thanks!

    Edit: looking at my question I think maybe I should have placed this question in Database Design...my apologies
    Last edited by MikeC; 05-26-2007, 05:24 PM. Reason: ??
    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
    __________________________________________




    #2
    Re: Conditional Report compared to many reports??

    Hi Mike,
    Have you ever noticed the preview feature in QB for its reports is actually a browse? If you are creating tabular reports this might work for you by running a query to display a browse on a temp table and printing from there. That way you could make a script where fields are selected that are used in creating the temp table. However if your report is anything like your last one I guess it wouldn't work!
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #3
      Re: Conditional Report compared to many reports??

      Thanks Robin for the info...something to consider for certain types of reports it sounds like. I have not seen this in action and would like to sometime to see exactly how it works---just may have to find someone I know with Quickbooks who uses its reporting capabilities to do so.

      And as you mentioned the reports I am referring to will be variations on the Report in my last thread posted ( http://msgboard.alphasoftware.com/al...ad.php?t=67364 )...for each conditional object I would have to create exactly what would have to be created in a regular single report so would not be a time savings as far as I can figure....and do not believe there is any overhead in calling up separate reports instead of one that would basically be filtered with the conditionals.
      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


        #4
        Re: Conditional Report compared to many reports??

        Mike, let me see if I can make a small sample for you. I have something similar where I create a temp table though not for a report. Perhaps I can adapt it.
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment

        Working...
        X