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

Date range on report

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

    Date range on report

    Many forms in my project are simply selection screens that provide the filter criteria to print a report. So that the reader is aware of the selection criteria, I like to include the variables in the header of the report. In the current project the user selects a range of dates on a form Var->Start_Date and Var->End_Date. The dates are used to filter records in the transaction file and both variables are included in the header of the report using the same format DTOC(Var->Start_Date,"4") for both. The start date prints, but the End Date does not. The report is filtered correctly so I know the variable still contains the correct value at the start of printing yet nothing I can do will print it on the header. Can anyone help with this? Thanks in advance.
    Tags: None
    #2
    Re: Date range on report

    Have you checked/compared the properties of the variables on the report? The display characters may not be enough to make it visible.
    There can be only one.

    Comment

      #3
      Re: Date range on report

      Thank you Stan for your quick reply. I have checked the display characters and even made the field extremely wide but I don't think that is the problem. Your first statement makes a lot of sense. Is there a utility in Alpha 5 that lets you view and compare all the variables in the project?

      Comment

        #4
        Re: Date range on report

        Not that I know. I was merely suggesting that you examine the properties of the two variables in the report header.

        Can you zip and attach the table here (from the control panel)?
        There can be only one.

        Comment

          #5
          Re: Date range on report

          The properties of the two variables Var->Start_Date and Var->End_Date are exactly the same. Could it be that one is Global and the other is Layout? Is there a way to check this?

          Comment

            #6
            Re: Date range on report

            Originally posted by pjstarr View Post
            The properties of the two variables Var->Start_Date and Var->End_Date are exactly the same. Could it be that one is Global and the other is Layout? Is there a way to check this?
            under

            http://wiki.alphasoftware.com/~alpha...oper+Functions - developer functions

            is

            http://wiki.alphasoftware.com/~alpha...IABLE+Function - to show variables
            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

              #7
              Re: Date range on report

              If the report filter sees the variables they both should be available to print in the report header.
              There can be only one.

              Comment

                #8
                Re: Date range on report

                Paul,

                Current_order and
                Current_filter

                are system variables available to your report layout.

                Have you considered using them in your reports to display the selection and ordering criteria?

                Comment

                  #9
                  Re: Date range on report

                  Thanks to all for your assistance. I was losing too much time trying to figure this one out so I just introduced a new global variable on the selection form called Ending_Date and replaced the variable that was not printing with the new one. Now everything is fine. One last question: How does one remove unused variables from the project?

                  Comment

                    #10
                    Re: Date range on report

                    Remove it in the place you created it. Might be in the form design mode.
                    There can be only one.

                    Comment

                      #11
                      Re: Date range on report

                      The project is ready for beta test. Thanks again everyone for all the help.

                      Comment

                        #12
                        Re: Date range on report

                        I always use a calulated field on a report - like

                        hdr="From " + var->bd + " Thru " + var->ed
                        note: there is no need to chage the date variable to a character value - alpha handles it just fine
                        Cole Custom Programming - Terrell, Texas
                        972 524 8714
                        [email protected]

                        ____________________
                        "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                        Comment

                          #13
                          Re: Date range on report

                          Martin, that's exactly the method I used, except var->ed was always blank. I convert the dates using DTOC(date,"4") so they display in the "December 31, 2013" format.

                          Comment

                            #14
                            Re: Date range on report

                            It will only be blank if you didn't force both a from and thru
                            also, if it didn't show all of the calculated field, it may be the width is not great enough and the format is to small
                            Cole Custom Programming - Terrell, Texas
                            972 524 8714
                            [email protected]

                            ____________________
                            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                            Comment

                            Previous template Next
                            Working...
                            X