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

Bottom Records

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

    Bottom Records

    I have a checkbook dbf which is sorted by paid date. In order to print the last 65 records of a particular month, I set up a global variable called enddate. I then use the following expression in order to get the last 65 records to print them.

    rep_filter = "bottom_records(65,\"\") .and. cdate(paiddate)<=cdate(enddate)"

    The output I am getting though is not the last 65 records that meet the filter criteria, but the last 65 records of the checkbook database. Blanks are printed if the filter criteria is not met.

    For example, if enddate={03/31/09} and the last 5 records in the checkbook database have a paiddate of {04/01/09}, then I would only get 60 records printing.

    The question is how can I get the last 65 records for the filter requested?

    Thanks,

    Charlie

    #2
    Re: Bottom Records

    rep_filter = "bottom_records(65,cdate(paiddate)<=cdate(enddate)) "

    I think will work.

    Or not.

    The question is how can I get the last 65 records for the filter requested?
    What 65 records do you want? The last 65 in enddate order, paiddate order?

    Always easier to check these things with a sample database than to try to imagine what will happen.
    Last edited by Stan Mathews; 04-01-2009, 01:52 PM.
    There can be only one.

    Comment


      #3
      Re: Bottom Records

      Thanks Stan. Enddate is simply the global variable of a date where the last record should be. The dbf is sorted in paiddate order, so at any time I want to plug in a variable enddate and get the 65 records that precede that date. What I am getting now is just the last 65 records in the dbf.

      I'll try your expression.

      Charlie

      Comment


        #4
        Re: Bottom Records

        Stan,

        Sorry, your expression did not work and I got an invalid report filter error.

        I even tried filtering the dbf prior to issuing the bottom_record request, but that didn't help (and logically I can understand that).

        Any other ideas?

        Charlie

        Comment


          #5
          Re: Bottom Records

          rep_filter = "bottom_records(65,\" paiddate<=var->enddate\")"

          Comment


            #6
            Re: Bottom Records

            Had to go read up on this process.

            The term "bottom" does not imply that record values are examined. "Bottom" means last, given the current sort order.
            So I think you need a button on a form, based on the table, to query the table and then base the report on current selection of records..

            Code for button...
            Code:
            dim tbl as P
            dim inx as P
            tbl = table.current()
            query.filter = "bottom_records(65,\"cdate(paiddate)<=cdate(enddate)\") "
            query.order = "paiddate"
            inx = tbl.query_create()
            topparent.resynch()
            report.print("yourreportname")
            There can be only one.

            Comment


              #7
              Re: Bottom Records

              Gabriel: This change makes no difference in the code.

              Stan: I tried that during one of my iterations to come up with a solution. The only other thing that I was thinking about was possibly creating a new index in the button code based on the variable input of enddate. Then, like the counting of records, it might work. I mention counting of records only because, as you know, a record count counts all records in the database even if it is filtered. The only way to get a proper record count is to create an index and then count the records that match that index.

              Another, (more painful) way, would be to copy the records in question to another temp dbf and then run the report from there.

              I'll try those ideas and get back to you. In the meantime, if you think of something more elegant, let me know.

              Charlie

              Comment


                #8
                Re: Bottom Records

                The last syntax is the correct syntax. The problem I believe is in how you are using: rep_filter

                Comment


                  #9
                  Re: Bottom Records

                  Gabriel,

                  Nice picture of you. I hadn't seen that before!

                  Did George Bernard Shaw actually say that? I didn't know he used Sham Wows!

                  Charlie

                  Comment

                  Working...
                  X