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
Devcon 2020 Goes Virtual! LEARN MORE >

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

One report to "fit" all

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    One report to "fit" all

    I've created a "Sales" report that displays info about each job that leaves my customer's plants (customer, date billed, descript., quoted price, jobcost, etc.). Right now it has some flexibility in that I have created a filter based on 2 variables -- begin_date and end_date (Bill_Date>=VAR->BEGIN_DATE.AND.Bill_DateEnd_Date) -- and ordered by company and bill_date. This allows us to do a daily, weekly, monthly, quarterly, yearly, etc. report on whatever dates my customer wants a report on.

    But they'd like to have other options for displaying the same summary sales info and I'd like to do it w/o having to create additional copies of this same report for each specific filter, since the format of this report will work well for all the variations we've thought about so far. For instance, I'd like to be able to also filter on what plant the job was produced at; show jobs belonging to just one customer; job types, jobs of a certain dollar amt.; etc. In the parent table of the set I have a field for "customer," "plant," "job_type," etc., so I can create filters like the bill_date one above. So far I haven't been able to get multiple filters to work with this one report. Can it be done? Again, many thanks for all of the help I find here - Alpha is far more useful and valuable BECAUSE of the phorum!
    Tags: None
    #2
    RE: One report to

    How about this:

    Create a ui_get_list, which shows the user a list of the possibilities you mentioned. When they select the one they want, that item runs a script that previews the report, with the report.preview() command containing the report's filter (and, if necessary, sort order). Then make sure the report itself has no filter.

    I know this is somewhat brief. Write to me if you need more details.

    Bill

    Comment

      #3
      RE: One report to

      Hi Bill,

      I do a similar thing in one of my apps. All I do is copy the first
      report, give it an appropriate name, then change the ordering and
      filtering expressions, then from the main menu I call that specific
      report from a button on the main menu. There are many more
      sophisticated ways of doing this, but it is very easy with this
      approach.

      efs

      Comment

        #4
        RE: One report to

        Bill,

        Perhaps one approach would be to train them how to use Query by Form. Change your report layout to use the currently selected records. Then they can use QBF to set the desired 'view' they want covered in the report, following which they immediately run the report. Whatever records they've selected using QBF will appear in the report, and only those records.

        QBF is very powerful and flexible. The discussion in Ch. 3 of the User's Guide might be a good place to begin their training.

        --tom

        Comment

          #5
          RE: One report to

          I develop a form that runs before the report is viewed/printed. On that form, I let the user select/set different variable/fields that will be used in the report.
          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

            #6
            RE: One report to

            Guys:

            Got an Idea and it works.

            For instance I use report filters almost exclusively [don't do queries good yet]. The filter will be 'between datevar1 and datevar2' .AND. *any(code,var->custno). When custno is empty, it reports on everyone - conversely when custno HAS a value it processes only those with a code that matches. I've even tagged two *any statements along with the date sort and both work flawlessly.

            Just another idea of many.

            Ken

            Comment

              #7
              RE: One report to

              Guys:

              Got an Idea and it works.

              For instance I use report filters almost exclusively [don't do queries good yet]. The filter will be 'between datevar1 and datevar2' .AND. *any(code,var->custno). When custno is empty, it reports on everyone - conversely when custno HAS a value it processes only those with a code that matches. I've even tagged two *any statements along with the date sort and both work flawlessly.

              Just another idea of many.

              Ken

              Comment

                #8
                RE: One report to

                I live by the QBF. To add to what Tom said, I have a single report that performs many functions. The detail portion of the report never changes. What I did to make the report flexible was that I added a title to the report that when the report is run after the QBF it will ask for the operator to input a title. This technique has saved me much much time.

                One example is that at the end of the year of my customers will call and ask for a listing of all the items that they purchased for the year and quantities. With this one report I can do as many customers as I wish and customize it because I can put THEIR name in the tile.

                Comment

                Previous template Next
                Working...
                X