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

Matching ui_get to field?

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

    Matching ui_get to field?

    I need to print different text as to whether the ui_get_date matches the field Date, how do I write the IF statement for the calculated Text Field?
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    #2
    RE: Matching ui_get to field?

    Keith,

    I would think that it would be better to use a variable to
    hold the text & change the text depending on whether or not
    ui_get_date() is equal to the tables date field.

    ....This syntax should work for the calc field as well,
    just replace the var->text with the name of the calc field....



    tbl=table.curent()
    date1=ui_get_date("Date","Enter The Date You Want")
    if CTOD(date1)= tbl.datefield THEN
    tbl.change_begin()
    var->text= "Enter the text you want here"
    tbl.change_end(.t.)
    else
    'if ui_get_date() is not equal to the date field
    tbl.change_begin()
    var->text= "Enter the text you want here"
    tbl.change_end(.t.)
    end if
    end

    Comment


      #3
      RE: Matching ui_get to field?

      Keith-
      Two ways to get user entered dates into reports...

      1. Create GLOBAL variables (maybe SESSION variables will pass depending on context)

      2. ASK USER variables. The ui_get_date() is an xbasic interaction rather than a report printing function. When getting user entered dates in reports use ASK USER variables. ASK USER variables can be set up in the report filter section or the report calc fields section. Once used these variables show up as variables with ASK_D_your_question on the drop down field lists.

      Use them as any other variable.

      If I read your question right all you need is in Report define a Calculated field as

      Text = if(ASK_D_Enter_Date=Date,"Dates match text",
      "Dates don't match text")
      and put Text where you need it...

      Comment


        #4
        RE: Matching ui_get to field?

        Doug

        Thanks for reply, I think you are are the right path. This is what I am trying to achive: to print a report for a driver to make either a collection or delivery that is required on the date that the report is reqested for, and only the correct instruction for that date will be printed.

        eg. field date_1= 13/12/2000
        field instr_1 = Collection
        field date_2 = 18/12/2000
        field instr_2 = Delivery

        So far I am able to print a report for the selcted date regardless whether it is a Collection or Delivery, now all I want is to make sure that both instructions cannot be printed on the report for the one Date that was called for with the ui_get_date request.
        Regards
        Keith Hubert
        Alpha Guild Member
        London.
        KHDB Management Systems
        Skype = keith.hubert


        For your day-to-day Needs, you Need an Alpha Database!

        Comment


          #5
          RE: Matching ui_get to field?

          Keith

          when you print the report you will have some sort of filter to pick the date. This will show up as a variable in the fields available to choose from in the reports expression builders.

          Text=if(Rept_date=Date_1,Instr_1,if(Rept_date=Date_2,Instr_2,""))

          A nested if statement, checks the match on collection, the delivery, if no match is an empty string which won't print anything and if you want the report can shrink appropriately

          Comment


            #6
            RE: Matching ui_get to field?

            Stephen

            Thanks for you help so far. The reason I was useing ui_get_date in a script was that I was calling for the report by clicking a button on a form. And this then selected the dates of the customers I wanted visited on that date. Can you please tell me how to use the variable created at the form page that I can use against for calculated fields on the report, I am not sure how to use the global command.

            Keith.
            Regards
            Keith Hubert
            Alpha Guild Member
            London.
            KHDB Management Systems
            Skype = keith.hubert


            For your day-to-day Needs, you Need an Alpha Database!

            Comment


              #7
              RE: Matching ui_get to field?

              If you define a variable on the form page the very first property is the level - choices are layout, session or global.

              I am not sure but a session variable may pass to a report...Certainly a global variable will. The thing with global variables is once created they stay in memory until Alpha Five quits, unless you issue a DELETE command. And if you use the same variable names you could stumble over old values...

              Another glitch is once you decide to use the global variable created in a form, you have to be sure it exists before you run the report else the report will crash...

              Which is why I use the ASK variables - they are created within the report definitions and do not stick around afterwards.

              Comment


                #8
                RE: Matching ui_get to field?

                Stephen and you other guys, thank you for your help, with bit of this and that I have got what I wanted so far. Now I would like to try one more thing. I have a field for customers "addr1" and a field for "del1". The addr1 is filled from a lookup table, what I want to do is fill "del1" with "addr1" if 'check box' "same" is checked and if not then a new delivery address can be entered in.
                Thanks in advance, I know you will come up with the answer.

                Keith Hubert
                Regards
                Keith Hubert
                Alpha Guild Member
                London.
                KHDB Management Systems
                Skype = keith.hubert


                For your day-to-day Needs, you Need an Alpha Database!

                Comment


                  #9
                  RE: Matching ui_get to field?

                  Keith-
                  Put code in the OnChange event of the checkbox object on the form.
                  You might try using the Action Scripting tools for this...
                  1. GET the value of "addr1" into a variable
                  2. SET the value of "del1" to this variable
                  If it seems apropriate...
                  3. Activate the next logical field, considering you just filled "del1"

                  Steve

                  Comment

                  Working...
                  X