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

filter help please

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

    filter help please

    i have 2 tables linked in a set on the acct number. one has all of the cust info, the other the transactions. i am trying to filter just the unique transactions for each acct on a certain date, in this case, 2 days ago. i keep getting multiple transactions for each acct in the report. what am i doing wrong? i tried a few variations of this formula, to no avail.

    Acct>0.and.unique_key_value().and.Custpts->Transdate>(date()-2)

    #2
    Gary, you haven't described the set explicitly. I assume the link from cust info to transactions is one to many. If not, ignor all that follows.

    What do you mean by "just the unique transactions". Why would any single customer have duplicate transactions in the related table?

    What are "multiple transactions"? Are you saying multiple copies of the same transaction? I should think multiple (distinct) transactions would be expected.

    Like to help, but I don't understand your problem.

    -- tom

    Comment


      #3
      hi tom:

      sorry for the confusion. it is a one to many link (but i tried first match, too). some customers have multiple transactions on the same day, as well as throughout the year. there are customers that shop almost every day, so there are a lot of transactions for some of them. i was working with 2 days because there are millions of transactions in the table.

      what i'm really looking for is, any customers that haven't shopped in a given period of time so a mailer can be sent. but i could not even get a unique list of customers that have shopped in the last 2 days.

      let's say a customer shopped 20 times in the last 6 months, i only wanted them listed once in the report, but no matter what i tried with the unique_key _value, i would get multiple listings.

      Comment


        #4
        Gary, it'd be nice if the transaction date field in your child table posted to a "Last Shopped" date field in the Cust Info table, wouldn't it? I think a table field rule (using the replace field value option) would do the trick. Then you simply filter the Cust Info table for folks who have field values that do NOT fall BETWEEN the (current date - 180 days) and (current date).

        Assuming this isn't possible, here's one approach, albeit a clumsy one. The difficulty here is that you're trying to print a report for records that "aren't there". i.e. for customers who DON'T have a transaction within the specified date range.

        1) unmark all Cust_info records
        2) create inverted set. Transactions (parent) linked 1:1 to Cust Info
        3) Query the set for all records where the Transaction date falls in the date range (use the BETWEEN() function)
        4) Mark all Cust_info records while the query remains in effect

        You've just marked the customers who have transactions in the specified date range.

        Now it's easy.

        5) print your report but using a filter that only includes Cust_info records that are .NOT. Marked().

        -- tom

        Comment


          #5
          i'll give it a try, thanks tom

          Comment

          Working...
          X