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

Help with Creating an Append Operation that prompts for date range

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

    Help with Creating an Append Operation that prompts for date range

    I would like to create an Operation that Appends data from one table to another based on InvDate being between 2 dates the user specifies and posted<>"Y". Also, I'm not sure how to prompt for date range
    Tags: None
    #2
    Re: Help with Creating an Append Operation that prompts for date range

    Nevermind I got it.

    Comment

      #3
      Re: Help with Creating an Append Operation that prompts for date range

      Originally posted by rmi111er View Post
      Nevermind I got it.
      Our rules clearly state that a self-answered question contain the solution.....

      Sure makes it nice for other users who find this issue when they search...
      Al Buchholz
      Bookwood Systems, LTD
      Weekly QReportBuilder Webinars Thursday 1 pm CST

      Occam's Razor - KISS
      Normalize till it hurts - De-normalize till it works.
      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
      When we triage a problem it is much easier to read sample systems than to read a mind.
      "Make it as simple as possible, but not simpler."
      Albert Einstein

      http://www.iadn.com/images/media/iadn_member.png

      Comment

        #4
        Re: Help with Creating an Append Operation that prompts for date range

        I did an append operation and added the below as my filter
        between(Invdate,var->AskD_Enter_Start_Date,var->AskD_Enter_End_Date)

        Comment

          #5
          Re: Help with Creating an Append Operation that prompts for date range

          Excellent. Thanks for sharing..
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment

            #6
            Re: Help with Creating an Append Operation that prompts for date range

            I am using the Append genie to do something similar. But when I run the append it tells me the master field in the filter doesn't exist! This is what the genie created for my filter:

            "paydate = Var->askD_What_Date"

            The error message shows the filter parsed correctly as: "Paydate = {12/14/2012}"

            Any ideas what is going wrong? I tried converting the processed XB to a script so I could try:

            "paydate = "+s_quote(var->askD_What_Date)

            but that didn't work either.
            Attached Files
            Robin

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

            Comment

              #7
              Re: Help with Creating an Append Operation that prompts for date range

              Well I couldn't get the append to work with a date but found a work around that accomplished what I needed - I used a calculation with a lookup function in field rules and then in a button on the form put all the records in the browse in change mode to get the calculated field to update with the info from the other table. The button then opens another form so the update occurs seamlessly. Nice thing about Alpha is that there is more than way to accomplish a goal.
              Robin

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

              Comment

                #8
                Re: Help with Creating an Append Operation that prompts for date range

                Nice but elaborate way to resolve, I can't even fully follow. Now doing an update instead of filtered append.
                Question is, why is PAYDATE not recognised (we also use English spelling) as a valid field?
                If you have an example...

                Comment

                  #9
                  Re: Help with Creating an Append Operation that prompts for date range

                  Could it be by chance that the filter should be for the transaction table?
                  Tim Kiebert
                  Eagle Creek Citrus
                  A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                  Comment

                    #10
                    Re: Help with Creating an Append Operation that prompts for date range

                    Originally posted by Tim Kiebert View Post
                    Could it be by chance that the filter should be for the transaction table?
                    Hi Tim,
                    No, I am updating a subset of master records for a particular payroll so I need to limit those records by the current paydate. The records are matched on a common field COANO to update the master COADESC field. Running an append would be the simplest way to do this, but my field rule will do the job if the records are changed. Since I use a button to go to the next step which is to export this data into Quickbooks, the button accomplishes the update so when the user views the records to export, they are complete.
                    Robin

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

                    Comment

                    Previous template Next
                    Working...
                    X