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

Radio buttons based on months

Collapse
X
Collapse
 
  • Page of 3
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
    #16
    Re: Radio buttons based on months

    Denis,

    I think the link that I gave you to Steve Wood gives you that code (or at least the framework for it). If I had more time, I would look into it. I don't mean to blow you off, but I'm real busy and don't have time to investigate it. Sorry.
    Peter
    AlphaBase Solutions, LLC

     [email protected]
    https://www.alphabasesolutions.com

    Comment

      #17
      Re: Radio buttons based on months

      Has anyone done this?

      I would have thought in-order to use the radio buttons in the search part, i could place some code within the after search event, which refers to the selection made from the radio buttons.

      Comment

        #18
        Re: Radio buttons based on months

        Originally posted by den1s View Post
        Has anyone done this?

        I would have thought in-order to use the radio buttons in the search part, i could place some code within the after search event, which refers to the selection made from the radio buttons.
        I've never done what you are trying to do however, were I to, I'd do it like this.

        1) Make computed field in the grid that gives you the 30 day ranges you want.
        For example in computed fields something like this:
        ExpSearchFld = iif(FieldInTable-Date() <= 30, "30",iif(FieldInTable-Date() > 30 .and. FieldInTable-Date() <= 60,"60","Over 60"))

        2) Make a search pull down with the representation of the values you get from the computed fields in step 1). eg "30", "60", "Over 60" in a dropdown for ExpSearchFld.

        Hope that helps :D

        Comment

          #19
          Re: Radio buttons based on months

          Clint,

          I have just got round to trying your suggestion.

          I think we are very close to success. I have modified the code to apply to my criteria.

          Code:
          ExpSearchFld     = iif(warranty_expiry-Date()<=30,"30",iif(warranty_expiry-Date()<=60,"60",iif(warranty_expiry-Date()<=90,"90","Over 90")))
          RESULTS:

          30 days
          20/11/2006
          11/12/2006

          Is it right that 30 days shows dates in the past?

          60 days
          10/01/2007
          11/01/2007

          Why does 60 days not show the items within the 30 days criteria?

          90 days
          10/12/2007
          11/12/2007
          01/01/2008

          Why does 90 days show the 2008 entry?

          Over 90 days
          01/01/2008

          This one seems logical.

          Any ideas.

          Thanks

          Denis
          Last edited by den1s; 12-07-2006, 02:35 PM.

          Comment

            #20
            Re: Radio buttons based on months

            Originally posted by den1s View Post
            Clint,

            I have just got round to trying your suggestion.

            I think we are very close to success. I have modified the code to apply to my criteria.

            Code:
            ExpSearchFld     = iif(warranty_expiry-Date()<=30,"30",iif(warranty_expiry-Date()<=60,"60",iif(warranty_expiry-Date()<=90,"90","Over 90")))
            RESULTS:

            30 days
            20/11/2006
            11/12/2006

            Is it right that 30 days shows dates in the past?

            60 days
            10/01/2007
            11/01/2007

            Why does 60 days not show the items within the 30 days criteria?

            90 days
            10/12/2007
            11/12/2007
            01/01/2008

            Why does 90 days show the 2008 entry?

            Over 90 days
            01/01/2008

            This one seems logical.

            Any ideas.

            Thanks

            Denis


            Hi,

            Try this:

            = iif(warranty_expiry-Date()<=30,"30",iif(warranty_expiry-Date()<=60 .and. warranty_expiry-Date()>30,"60",iif(warranty_expiry-Date()<=90 .and. warranty_expiry-Date()>60,"90","Over 90")))

            Comment

              #21
              Re: Radio buttons based on months

              Clint,

              Thanks for the quick reply, but i am getting exactly the same results. Could it be anything to do with the date format (i.e. UK dd/mm/yyyy)?

              Denis

              Comment

                #22
                Re: Radio buttons based on months

                Clint,

                I have tried seperating the syntax and it works, but i really need to work out how to run it from a single dropdown or radio button set. At the moment its unusable....

                Code:
                DateSearch30     = iif(warranty_expiry-Date()<=30,"30","0")
DateSearch60     = iif(warranty_expiry-Date()<=60,"60","0")
DateSearch90     = iif(warranty_expiry-Date()<=90,"90","0")
DateSearcho90    = iif(warranty_expiry-Date()>90,"over 90","0")
                What do you think?

                Denis

                Comment

                  #23
                  Re: Radio buttons based on months

                  Originally posted by den1s View Post
                  Clint,

                  I have just got round to trying your suggestion.

                  I think we are very close to success. I have modified the code to apply to my criteria.

                  Code:
                  ExpSearchFld     = iif(warranty_expiry-Date()<=30,"30",iif(warranty_expiry-Date()<=60,"60",iif(warranty_expiry-Date()<=90,"90","Over 90")))
                  RESULTS:

                  30 days
                  20/11/2006
                  11/12/2006

                  Is it right that 30 days shows dates in the past?
                  I see what you mean...

                  60 days
                  10/01/2007
                  11/01/2007

                  Why does 60 days not show the items within the 30 days criteria?
                  I get you now you mean 60 and less to include those already in the 30 and less group
                  90 days
                  10/12/2007
                  11/12/2007
                  01/01/2008

                  Why does 90 days show the 2008 entry?

                  Over 90 days
                  01/01/2008

                  This one seems logical.

                  Any ideas.

                  Thanks

                  Denis
                  New logic:

                  = iif(warranty_expiry-Date()<=30 .and. warranty_expiry-Date()>=0,"30 and under",iif(warranty_expiry-Date()<=60 .and. warranty_expiry-Date()>=0,"60 and under",iif(warranty_expiry-Date()<=90 .and. warranty_expiry-Date()>=0,"90 and under",iif(warranty_expiry-Date()>90,"90 and Over","PastDue"))))

                  Try this as your calc field. You end up with the string (that you can search for) which represents the date ranges in question.

                  Comment

                    #24
                    Re: Radio buttons based on months

                    Thanks Clint.

                    I applied your new logic with the following results;

                    30 days
                    11/12/2006

                    Perfect !

                    60 days
                    10/01/2007
                    11/01/2007

                    60 and less not computing.

                    90 days
                    10/12/2007
                    11/12/2007

                    Got rid of the 2008 entry, but not displaying the previous dates.

                    90 days and over

                    01/01/2008

                    Seem ok! but no previous dates.

                    Thanks for all your help with this one.

                    Denis
                    Last edited by den1s; 12-08-2006, 03:56 AM.

                    Comment

                      #25
                      Re: Radio buttons based on months

                      I am stumped on printing a PDF from a Grid, so i have now reluctantly reverted to a dialog. Can someone advise me on how i can use the code below within a dialog.

                      = iif(warranty_expiry-Date()<=30 .and. warranty_expiry-Date()>=0,"30 and under",iif(warranty_expiry-Date()<=60 .and. warranty_expiry-Date()>=0,"60 and under",iif(warranty_expiry-Date()<=90 .and. warranty_expiry-Date()>=0,"90 and under",iif(warranty_expiry-Date()>90,"90 and Over","PastDue"))))

                      Comment

                        #26
                        Re: Radio buttons based on months

                        I have this but i am not sure how to also filter on the dates incorporating the above filter code;

                        Code:
                        DIM filter as C
DIM order as C
DIM filename as C

filter = "Type = " +quote(type) [B].and. "Warranty_Expiry = " +quote(Warranty_Expiry)[/B]
Order = ""
filename = session.session_folder + chr(92) + "tempreport.pdf"
filename = report.saveas("rptWarranty_Rep@<adb_path>\assets.ddd","pdf", filter, order, filename,.f.)
if file.exists(filename)
    currentform.RedirectTarget = session.session_url + "tempreport.pdf?" + rand_string(5)
end if
                        Last edited by den1s; 12-11-2006, 10:39 AM.

                        Comment

                          #27
                          Re: Radio buttons based on months

                          Originally posted by den1s View Post
                          I am stumped on printing a PDF from a Grid, so i have now reluctantly reverted to a dialog. Can someone advise me on how i can use the code below within a dialog.

                          = iif(warranty_expiry-Date()=0,"30 and under",iif(warranty_expiry-Date()=0,"60 and under",iif(warranty_expiry-Date()=0,"90 and under",iif(warranty_expiry-Date()>90,"90 and Over","PastDue"))))
                          In an unrelated aside. To print a PDF from a grid, simply make a link that goes to a intermediate page that issues your create PDF logic.

                          Comment

                            #28
                            Re: Radio buttons based on months

                            Originally posted by den1s View Post
                            I have this but i am not sure how to also filter on the dates incorporating the above filter code;

                            Code:
                            DIM filter as C
DIM order as C
DIM filename as C

filter = "Type = " +quote(type) [B].and. "Warranty_Expiry = " +quote(Warranty_Expiry)[/B]
Order = ""
filename = session.session_folder + chr(92) + "tempreport.pdf"
filename = report.saveas("rptWarranty_Rep@<adb_path>\assets.ddd","pdf", filter, order, filename,.f.)
if file.exists(filename)
    currentform.RedirectTarget = session.session_url + "tempreport.pdf?" + rand_string(5)
end if
                            If you're using a dialog to specify the filtered field value, create a session variable in that dialog. Then response redirect to the new page with the grid and filter on the calculated field you made using the IIF (immediate IF calc). Don't mess with dates, use the calculated field instead.

                            But why do that when you could use the search above the grid?

                            Comment

                              #29
                              Re: Radio buttons based on months

                              Clint,

                              Thank you for your persistance on this matter.

                              As i/we have done so much work on the grid and almost have it working. Can you help me with the syntax to make a link that goes to a intermediate page that issues my create PDF logic.

                              Comment

                                #30
                                Re: Radio buttons based on months

                                Originally posted by den1s View Post
                                Clint,

                                Thank you for your persistance on this matter.

                                As i/we have done so much work on the grid and almost have it working. Can you help me with the syntax to make a link that goes to a intermediate page that issues my create PDF logic.
                                You are welcome, here you go.

                                Make a link to an a5w page (that you create in advance, PrintBid.a5w in my example) as in pic below. I use a calculated field to make the link pretty, that is optional.


                                In your a5w page, put code like this below.
                                Code:
                                dim filter as C

dim order as C

dim filename as C


Filter = "tkey = " + quote(session.__protected__TKEY)

Order = ""

filename = session.session_folder + chr(92) + "tempreport.pdf"

filename = report.saveas("BidCover@[PathAlias.ADB_Path]\Bidinfo.set", "pdf",filter, "", filename, .f.)
 

if file.exists(filename) 

    response.redirect(session.session_url + "tempreport.pdf?" + time("hms3"))

end if

 

end
                                In your case, you're going to filter on the calculated field you made in the grid.

                                I'm hoping for better examples in the new version. Better help in general. Subdivided by desktop versus WAS would be peachy.

                                Type advanced button in the help search and watch the insanity.

                                /waves at Alpha wink wink nudge nudge :D

                                Comment

                                Previous 1 2 3 template Next
                                Working...
                                X