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

Operations : Unexpected behaviour

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

    Operations : Unexpected behaviour

    I defined an operation to select records from a table. I defined the operation to prompt for a beginning date and an ending date for a date field. When the operation is run, a dialog box pops up asking for the dates. So that's good.

    I then defined another Operation to summarize records from the same table. In defining this Operation I included the option to filter the records and to use the filter operation.

    When I run the 2nd operation I do not get the prompt from the 1st operation... shouldn't I get that prompt for the dates?

    The 2nd operation does use the 1st operation.

    If I execute the 1st operation the date selection box pops up.
    If I then execute the 2nd operation it does work but just picks up the dates lasted entered when the 1st operation ran.

    Is this supposed to work this way. I expected the 1st operation to prompt for the dates no matter now it is run.

    David

    #2
    Re: Operations : Unexpected behaviour

    Originally posted by Davidk View Post
    I defined an operation to select records from a table. I defined the operation to prompt for a beginning date and an ending date for a date field. When the operation is run, a dialog box pops up asking for the dates. So that's good.

    I then defined another Operation to summarize records from the same table. In defining this Operation I included the option to filter the records and to use the filter operation.

    When I run the 2nd operation I do not get the prompt from the 1st operation... shouldn't I get that prompt for the dates?

    The 2nd operation does use the 1st operation.

    If I execute the 1st operation the date selection box pops up.
    If I then execute the 2nd operation it does work but just picks up the dates lasted entered when the 1st operation ran.

    Is this supposed to work this way. I expected the 1st operation to prompt for the dates no matter now it is run.

    David
    It works the way it's set up and it sounds like it's not the way you want it. If you can post a working example, I'm sure you will get what you desire.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      Re: Operations : Unexpected behaviour

      an example would take the guesswork out of the equation....it almost sounds like you defined a date dialog box to show up with the first operation and not the second...and expected the data dialog box to appear for the second simply due to the operations being based upon the same table. ?????
      Mike
      __________________________________________
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau
      __________________________________________



      Comment


        #4
        Re: Operations : Unexpected behaviour

        Thanks for looking... here's an example.

        opSelectRecords selects record based on a date - it asks for a Start Date and an End Date.

        A funny thing though, when the prompt displays - it display backwards... the End Date is prompted for first.

        opSummary1 uses opSelectRecords as a filter. The Start Date and End Date are those last used when the opSelectRecords query was run. The operation does not prompt again - I think it should prompt every time.

        opSummary2 attempt to ask for Start Date and End Date but I can't get it to work. It prompts but no selection takes place.

        I guess "Filter" means an operation is supposed to be used.

        Comment


          #5
          Re: Operations : Unexpected behaviour

          Hi David,
          First, I have not yet checked out your attached example....but will do so for sure later on tonight ( if not resolved by then!).

          Regarding
          A funny thing though, when the prompt displays - it display backwards... the End Date is prompted for first.
          Am thinking this is most likely using Ask variables which are simplistic at best (have their uses though!)--they show up alphabetically and not in the order created....so change the Start date say to Begin date and the order wanted will be there.

          Off until later now---and will look into your issue first thing when back.
          Mike
          __________________________________________
          It is only when we forget all our learning that we begin to know.
          It's not what you look at that matters, it's what you see.
          Henry David Thoreau
          __________________________________________



          Comment


            #6
            Re: Operations : Unexpected behaviour

            Hi David,
            Yep....Ask Variables. In this case you would have to have at least a shared variable and no way to dimension the Ask Variables above a local.

            You are not calling the Ask Variables again in the opSummary1 operation....you are just trying to use the filter that was created by the opSelectRecords query....which it does try to use
            "between(Transdate,var->AskD_Beg_Date,var->AskD_End_Date)"
            , but as the values contained within the Ask variables are not dimensioned as shared/global, your other operation cannot see them.....

            For the second operation, opSummary2, you could use this for the filter which will work..
            Code:
            between(transdate,var->AskD_Beg_Date, var->AskD_End_Date)
            You could have your own dialog box come up (using action script if wanted) to have the date variables and then you can dim them as required to be utilized elsewhere.
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment


              #7
              Re: Operations : Unexpected behaviour

              Thank you Mike... that's great.

              Interesting bit about the ask variables... wouldn't mind that showing up in the help file as the first sentence. When I switched the variables around they still showed up backwards... makes sense (not really) now.

              I can see that using an existing query with pre-determined dates would have it's uses.

              Cheers.

              Comment


                #8
                Re: Operations : Unexpected behaviour

                There is something about this in the help and the fix was to define your ASK variables with a number order before the prompt.

                VAR->ASKD_1_Start_Date
                VAR->ASKD_2_End_Date
                Robin

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                Comment


                  #9
                  Re: Operations : Unexpected behaviour

                  Absolutly right... just read it...

                  Note : The variables will be displayed in alphabetical order.

                  Thanks.

                  Comment

                  Working...
                  X