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

Filter in report.saveas problem

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

  • Filter in report.saveas problem

    This one has me baffled (happens more and more lately!)

    I've created a few reports to print out of my web app, and created a dialog to select the report and various parameters. screen1 is the dialog. I select the client, select the job or jobs, date range, and various stuff, then do the report saveas as shown in the demo pages.

    Screen2 is the report. I've got two problems. First, the first job is filtered for the date range as it should be, but the second job shows all records for that job with no date filtering. The text attached shows my filter script.

    Second problem, and less important, is how do I print my date range on the report?

    Thanks,
    Pat
    Pat Bremkamp
    MindKicks Consulting

  • #2
    Filters may need to be different.

    Pat

    I see from your script that the 3 reports are based on different tables.

    One way of debugging this is to have your script save the filter that is generated to a file or have the filter show in a text box and then try to use that filter directly in the report. It may help show where the syntax variation is.
    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.

    Comment


    • #3
      Thanks, Al.
      That was just the idea I needed to troubleshoot the filter. Turns out, I just needed parens around F1.

      Now, how about putting my start date and end date on the report? I've created global variables vgStart_Date and vgEnd_Date on the report to hold the values, but I don't see the how to get the page variable into the report global variables.

      Pat
      Pat Bremkamp
      MindKicks Consulting

      Comment


      • #4
        Global variables

        A global variable should be available to a report for printing.

        Where are you dimming it? Try dimming at startup - either in autoexec or called from it and then you should see it on the report drop down list.
        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.

        Comment


        • #5
          A global variable dimmed in the Alpha Five or Web App Server desktop, including using an autoexec, CANNOT be seen by a web application. There is no intermingling of global or shared variables between web and desktop environments. And trust me, you don't want there to be.

          A report can see a global variable dimmed in the A5W page that makes report.saveas() call.

          Also remember that in a web app, there is typically no database open. And if you're on a shared server, the open database may not be the one you want anyway. This means that relying on an autoexec or startup form for a web app is almost guaranteed to fail.

          Originally posted by Al Buchholz
          A global variable should be available to a report for printing.

          Where are you dimming it? Try dimming at startup - either in autoexec or called from it and then you should see it on the report drop down list.

          Lenny Forziati
          Vice President, Internet Products and Technical Services
          Alpha Software Corporation

          Comment


          • #6
            Oops

            Should watch the forum that I'm in.....
            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.

            Comment


            • #7
              Originally posted by Lenny Forziati
              A report can see a global variable dimmed in the A5W page that makes report.saveas() call.
              Lenny,

              I dimmed two global variables in my AfterValidate script and assigned the values, then created global variables with the same name in my report design and put them on the report. Did not work; they did not show.

              Is there more to it than that?

              Pat
              Pat Bremkamp
              MindKicks Consulting

              Comment

              Working...
              X