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

Date Based dropdown list filter does not filter

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

    Date Based dropdown list filter does not filter

    I seem to have this problem in V6 and V7. I have a table that has only one field, a date field. I have set up a dialog component with a dropdown box. I am trying to filter the date and no matter what expression I use (the epxressions checked out fine in the epxression bulder) no filtering takes place.
    I set up another test dbf file also using dates and a dialog with a dropwdown box, same results. All values display. Character based dropdowns work fine. I can create a query that works fine with the same expression. Has anybody else seen this? Code from the component is noted below.

    Steve

    Code:
    With tmpl.Variable_Info[1]
    	.Fieldname = "DropDownBox1"
    	.Scope = "Local"
    	.DisplayFormat = ""
    	.DisplayUnFormat = ""
    	.Type = "D"
    	.Varname = "DROPDOWNBOX1"
    	.Controltype = "DropDownBox"
    	.DropdownBox.InLineStyle = ""
    	.DropdownBox.Type = "Dynamic"
    	.DropdownBox.StyleFieldIfError = .t.
    	.DropdownBox.ErrorInLineStyle = ""
    	.DropdownBox.Size = 1
    	.DropdownBox.selectStyle = "Single"
    	.DropdownBox.NotInListRule = "Add To List if Not Null"
    	.DropDownBox.Datasource = "DBF-Table"
    	.DropDownBox.Table = "c:\jfkdb\week_ending.dbf"
    	.DropDownBox.DisplayValueField = "Week_Ending"
    	.DropDownBox.StoredValueField = ""
    	.DropDownBox.maxchoices = 0
    	.DropDownBox.Filter = "Week_Ending > date()"
    	.InitialValue = ""
    	.Column.Hide = .f.
    	.Column.Heading = "DropDownBox1"

    #2
    you may have to set the filter by overriding the settings of the component.

    what you want is this:

    .DropDownBox.Filter = "Week_Ending > " + s_quote(date())



    this will result a filter property of:

    .DropDownBox.Filter = "Week_Ending > {10/10/2005}"

    which is what you want.

    Comment


      #3
      Selwyn:

      That did not work. I tried your expression in the choices section of the dialog control for filter. Also tried it in the advanced section as an overide. Same result, all records are displayed. Also, set it up as an overide on the page in the appropriate section. No go. Yet, the same filter expression works in querys and forms on the desktop. Thanks,

      Steve

      Code:
      Delete tmpl_week_ending
      DIM tmpl_week_ending as P
      tmpl_week_ending = a5w_load_component("week_ending")
      'Following code allows you to override settings in the saved component, and specify the component alias (componentName property).
      'Tip: Keep the componentName property short because this name is used in page URLs, and it will help keep the URLs short.
      'Each component on a page must have a unique alias (componentName property).
      with tmpl_week_ending
      	componentName = "week_ending"
      .DropDownBox.Filter ="Week_Ending > " + s_quote(date())
      end with

      Comment


        #4
        You have not overrwidden settings correctly.

        The property that you want to override is:

        Variable_info[1].DropDownBox.Filter = "Week_Ending > " + s_quote(date())

        Comment


          #5
          Still no filtering. Here is the code from the page.

          Steve

          Code:
          Delete tmpl_week_ending
          DIM tmpl_week_ending as P
          tmpl_week_ending = a5w_load_component("week_ending")
          'Following code allows you to override settings in the saved component, and specify the component alias (componentName property).
          'Tip: Keep the componentName property short because this name is used in page URLs, and it will help keep the URLs short.
          'Each component on a page must have a unique alias (componentName property).
          with tmpl_week_ending
          	componentName = "week_ending"
          Variable_info[1].DropDownBox.Filter = "Week_Ending > " + s_quote(date())
          end with

          Comment


            #6
            Attached is zip file with table and component.

            Comment


              #7
              I was able to duplicate the problem.
              It seems that Alpha Five is assuming that the field in the dropdown list is a character value.

              You can easily work around this by accomodating Alpha Five. When you define the choices for the Dropdown list, you can specify that the field to display is:

              "" + Date

              Rather than just:

              Date

              This will convert the field from a date value to a character value, and my solution will work.

              convert_type(date,"C")

              will also work just as well.


              On further reflection, there is an even easier solution.

              In the Dialog's Activate event, add this code

              dim date_list as c
              date_list = table.external_record_content_get("[PathAlias.ADB_Name]/invoice_header","''+date","date","date>" + s_quote(date())

              Then, when you define the choices for the dropdownbox, specify that it is a dynamic list that is bound to a variable. specify the 'date_list' variable.

              Comment


                #8
                Thanks Selwyn for the quick response and fix.

                Steve

                Comment


                  #9
                  Selwyn:

                  I am using you suggestion for the activate form property. It works fine on the local web. I receive this error from the server based WAS which is version 6 of course.


                  Errors in: event.Activate code:
                  The system cannot find the path specified.
                  PathAlias.ADB_Name]/week_ending.DBF

                  Is this due to the fact the this a feature available under v 7? If so, I can work around it until 7 is released. Thanks,

                  Steve

                  Comment


                    #10
                    Originally posted by Steve Bovino
                    Selwyn:

                    I am using you suggestion for the activate form property. It works fine on the local web. I receive this error from the server based WAS which is version 6 of course.


                    Errors in: event.Activate code:
                    The system cannot find the path specified.
                    PathAlias.ADB_Name]/week_ending.DBF

                    Is this due to the fact the this a feature available under v 7? If so, I can work around it until 7 is released. Thanks,

                    Steve
                    No, it has nothing to do with V7. You are not using any V7 features here. It does not look like the component was properly published, or perhaps the alias was not defined in your Profile when you published.

                    Your event code has this in it:

                    [PathAlias.ADB_Name]\week_ending.dbf

                    (you have written a forward slash. i presume you meant a backslash)

                    You should have a path defined for this alias 'PathAlias.adb_name' in your profile.

                    When you publish the component, the code in the event should have gotten changed to

                    c:\mydata\week_ending.dbf

                    (assuming that the alias [pathAlias.adb_name] was defined to be "c:\mydata". of course, in your case it will be different)

                    Comment


                      #11
                      For some reason when I publish this particular component the path alias is not being translated. here is the code from the component. I am not having this problem with other components.

                      Steve

                      Code:
                      %code%
                      tmpl.events.Activate = <<%code%
                      dim date_list as c 
                      date_list = table.external_record_content_get("PathAlias.ADB_Name]\week_ending","''+week_ending","week_ending","week_ending>" + s_quote(date()))

                      Comment


                        #12
                        corrected code from component Still not translating.

                        Code:
                        %code%
                        tmpl.events.Activate = <<%code%
                        dim date_list as c 
                        date_list = table.external_record_content_get("[PathAlias.ADB_Name]\week_ending","''+week_ending","week_ending","week_ending>" + s_quote(date()))

                        Comment


                          #13
                          What is the name of the Profile that you are publishing to?

                          How are the aliases for this profile defined?

                          Comment


                            #14
                            the profile is called LAN and the alias is defined as:

                            [PathAlias.ADB_Path] = c:\a5webroot\jfkdata

                            Comment


                              #15
                              It makes no sense to me that the alias would not be replaced by the actual value when the component was published. I don't know how this could happen. I have never seen it before.

                              You could just hard code the event script to use 'c:\a5webroot\jfkdata' in place of [PathAlias.ADB_Path] and then publish.

                              Comment

                              Working...
                              X