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

Invalid report filter expression...

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

    Invalid report filter expression...

    I have created, using action scripting, a query and print routine. We do batch billing for a few clients and print a weekly invoice list.

    I used an XDialog box to create variables for dates and the clients, and then there are 2 constants included in the query.

    This is set up to use to run this for 4 clients. It works fine for 3 out of the 4 clients. Since this is the same query and report for all 4 I am stumped as to why I get an error message.

    The dates that are input for the week are the same, the only thing that changes for each of the 4 runs, is the name of the client chosen. The report that is 'called up' is the same except for the client name that fills in dependent on the client name chosen for the query.

    SO -- How can it work for 3 of them and not the 4th??

    I get the following error message on that one......
    Invalid report filter expression:'Is_recno_in(table.recno_list(<<%RL0%42060 42069 42074 42082 42122 ....(lists the invoice numbers)...42418 "%RL0%))'.

    This is making me bonkers !!!!

    HELLP

    Thanks
    Terri
    Tags: None
    #2
    Re: Invalid report filter expression...

    Originally posted by TerriH
    I have created, using action scripting, a query and print routine. We do batch billing for a few clients and print a weekly invoice list.

    I used an XDialog box to create variables for dates and the clients, and then there are 2 constants included in the query.

    This is set up to use to run this for 4 clients. It works fine for 3 out of the 4 clients. Since this is the same query and report for all 4 I am stumped as to why I get an error message.

    The dates that are input for the week are the same, the only thing that changes for each of the 4 runs, is the name of the client chosen. The report that is 'called up' is the same except for the client name that fills in dependent on the client name chosen for the query.

    SO -- How can it work for 3 of them and not the 4th??

    I get the following error message on that one......
    Invalid report filter expression:'Is_recno_in(table.recno_list(<<%RL0%42060 42069 42074 42082 42122 ....(lists the invoice numbers)...42418 "%RL0%))'.

    This is making me bonkers !!!!

    HELLP

    Thanks
    Terri
    First thought is that if the list of invoice numbers is large enough it will be converted internally to blob data type rather than character and the is_recno_in() then has a wrong data type paramater.

    I'm not familiar with table.recno_list(). Is it in the documentation?
    There can be only one.

    Comment

      #3
      Re: Invalid report filter expression...

      Hi Stan
      Thanks for answering -- there were 77 invoices in this particular result - not a huge amount by any means

      I have tried to look up table.recno_list but do not come up with anything --
      It is nothing I personally put in but I do believe was generated from using the XDialog?? I really don't know --

      Any other ideas?

      Terri

      Comment

        #4
        Re: Invalid report filter expression...

        I have now tried to do the query adding a day at a time instead of the whole week. I was able to get up to 6 days without the error showing up -- when I made it the full week, the error message was back.

        So is there some validity to too many invoices and it changes the parameters?? If this is true, how do I fix it?

        Please let me know

        Thanks
        Terri

        Comment

          #5
          Re: Invalid report filter expression...

          Originally posted by TerriH
          I have now tried to do the query adding a day at a time instead of the whole week. I was able to get up to 6 days without the error showing up -- when I made it the full week, the error message was back.

          So is there some validity to too many invoices and it changes the parameters?? If this is true, how do I fix it?

          Please let me know

          Thanks
          Terri
          I can't see why the xdialog created the filter that way. You are filtering for some sort of client_id and date range? That shouldn't require any use of record numbers at all.

          Any possibility of attaching a small sample?
          There can be only one.

          Comment

            #6
            Re: Invalid report filter expression...

            Here is the query I am using

            (between(Invdate,Var->vbegin,Var->vend) ) .and. (( Var->vclient $ Client->Clientname ) ).and. (Inspections->Gs_pr > 0.00 ) .and. (Inspections->Relocknum="")

            I have attached a screen shot of the Dialog box too

            As you can see, nothing references record numbers ??

            Terri

            Comment

              #7
              Re: Invalid report filter expression...

              Terri,
              I don't know whether this is a button-based action or not, but have you tried rebuilding the script? Sometimes this has cured Bonkers for me.

              This might be an aside, but part of the filter has the following:
              Code:
              (( Var->vclient $ Client->Clientname))
              On the uniqueness and specificity scale, this if not a robust filter. Do you not have unique client numbers or something that provides more exact uniqueness parameters for the client?

              I have not seen the table.recno_list()function, and neither can I find documentation for it.

              Grasping (hugely) at the wind..is there some indexing parameters in place that points to record numbers? And also, is there a query.drop or show all records action between the 4 queries so that one query isn't within the previous query?

              Mike W
              Mike W
              __________________________
              "I rebel in at least small things to express to the world that I have not completely surrendered"

              Comment

                #8
                Re: Invalid report filter expression...

                Well, we didn't figure out what the real problem was but, by sitting down and working on it at the conference in Las Vegas, we finally did get Terri's script to work.

                The original script was an action script that first attempted to query the current form then use...
                query.filter = current_filter_expn()
                to define the query for the report.

                This was returning the strange filter expression that she showed in her initial post:
                Is_recno_in(table.recno_list(<<%RL0%42060 42069 42074 42082 42122 ....(lists the invoice numbers)...42418 "%RL0%))
                The << and %RL0% stuff makes no sense to me at all based on the description of the Is_recno_in function in the Help file and I can't even find anything in the Help file about "recno_list".

                The solution was actually quite simple. We eliminated the query on the current form and just passed the original filter (which worked fine in the query) directly to the report. Something like this:
                filter = "<The_Original_Filter>"
                report.preview( "<RptName>", filter )

                This also simplified the script considerably.

                I can only guess that there was an issue with the number of records found. The Is_recno_in() function doesn't list any maximum number but the problem only seemed to occur with the bigger customers which, of course, meant printing the most records. We didn't take the time to verify this or try to find the limit - the script works now and that was good enough.

                Comment

                  #9
                  Re: Invalid report filter expression...

                  Hi Cal,

                  A couple of comments that might explain things a bit:

                  Originally posted by CALocklin View Post
                  This was returning the strange filter expression that she showed in her initial post:
                  Is_recno_in(table.recno_list(<<%RL0%42060 42069 42074 42082 42122 ....(lists the invoice numbers)...42418 "%RL0%))
                  The << and %RL0% stuff makes no sense to me at all based on the description of the Is_recno_in function in the Help file and I can't even find anything in the Help file about "recno_list".

                  The <<%RL0%42060 42069 42074 42082 42122 ....(lists the invoice numbers)...42418 "%RL0% is a multi line list constant, which probably was generated by an internal S_Quote() function.

                  table.recno_list(), I have no idea!
                  Regards,

                  Ira J. Perlow
                  Computer Systems Design


                  CSDA A5 Products
                  New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                  CSDA Barcode Functions
                  CSDA Code Utility
                  CSDA Screen Capture

                  Comment

                  Previous template Next
                  Working...
                  X