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



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

Posting Pricing but Pricing not set Daily

  • Filter
  • Time
  • Show
Clear All
new posts

  • Posting Pricing but Pricing not set Daily

    I'm attempting to assign a price to a transaction based on the transaction date. There is a table with price changes and dates to post from BUT the prices don't change daily. So a post operation that uses "Date" as the linking key will only post prices to transactions that occurred on a price change day and the others remain blank. I'm needing the blank ones to have a price of the previous price change. Below is an example of the "Price Change Table" where changes are stored and what the "Transaction Table" should look like after the posting/update. I'm hoping there is a simple solution and I apologize if it's too simple to be asking!

    Price Change Table
    7/1 1.00
    7/3 2.00
    7/5 3.00
    7/7 4.00
    Transaction Table
    7/1 1.00
    7/2 1.00
    7/3 2.00
    7/4 2.00
    7/5 3.00
    7/6 3.00

  • #2
    I think you need a part number (or item number) field to link on; not the date. If it's applicable to all lines, just leave the field always blank.

    Then, assuming you are using 8 character date fields, you could use replace on the price if the date in the transaction table is >= to the date in the price change table.

    So, for 7/6 in the above example, it would put in $1, then replace with $2, then replace with $3 never getting to the $4.

    But the above is sloppy and slow.

    You might consider instead adding a finish date field to the price change table allowing the transaction date to fall within a range.


    • #3
      My guess is that using a post operation is not the method to accomplish what you are attempting unless you update the price change table daily.
      Mike W
      "I rebel in at least small things to express to the world that I have not completely surrendered"


      • #4
        I think Mike's point deserves elaboration. "Operations" in AA are intended to be used when appending, deleting, updating or changing multiple records in one step. There are other techniques available to change a field in a specific transaction record. If you mean to post prices to multiple records in a single operation I think you'll find the post operation can't be programmed to do what you wish, where your "source" table has gaps. I see two alternatives:

        1) change your source table so that there's a date and price for every day in the year; or

        2) write a custom xbasic script that steps through the transactions and for each one: searches for a matching date in the source table; if found, change the price in the current transaction record - if not found, search again, for the previous date ... continue searching backwards til a match is found; change the price in the current transaction record.


        • #5
          Sorry to be blunt, but this is not a good design.
          In engineering,there are data called Effectivity Dates. Start and end of a period when a value or part is covered.

          In the request, the users don't have to enter a date for the item? That's not good. As Craig says, you need a common field - say an ID to relate the price to.
          Then, instead of an iteration as Tom suggested, if date doesn't exist, use a filter to get the LAST record where the ID's match as a Default Vaule.

          In the real world, I suspect there are date ranges when item prices vary up or down, so the base design needs a good look at, may I suggest?
          Ted Giles
          Example Consulting - UK

          See our site for Alpha Support, Conversion and Upgrade.


          • #6
            Thank you all for your input! I'm still trying to get my head around it all...

            In the actual tables there are Product Codes that can be linked as a common field. I'm able to have a start and end date in the "Price Change Table" but am unsure of what operation I should use to get the pricing over to the transaction table. Below are examples of what I have, and what I'm trying to accomplish with the added Product Code and End Date. I'm not sure if this makes a difference in they type of operation but the transaction table will end up being quite large (100-1000 transactions a day x 18-24 months).
            Pricing Table
            Product ID Start Date End Date Price
            001 1/1 1/15 $1.25
            001 1/16 1/20 $1.50
            001 1/21 1/30 $1.75
            002 1/1 1/15 $3.00
            002 1/16 1/20 $3.25
            002 1/21 1/30 $3.50
            Transaction Table
            Product ID Date Price
            001 1/2 $1.25
            001 1/18 $1.50
            001 1/25 $1.75
            002 1/3 $3.00
            002 1/19 $3.25
            002 1/21 $3.50


            • #7
              an additional note: I have a logical field in the transaction table to note if the transactions have been billed. Once they are billed, the prices shouldn't be able to be altered ( i.e. changes to pricing table on accident?)


              • #8
                Is this an Invoicing Application?

                If so, there is more information needed in order to process the transactions.
                I am presuming that;
                Customer buys item
                Price of item is dependent on a date range
                Transaction Table holds details of customer, price, quantity and billing/paid flag
                Invoice is created from the Transaction Table.

                Close or not close?​​​​​​​
                Ted Giles
                Example Consulting - UK

                See our site for Alpha Support, Conversion and Upgrade.


                • #9
                  It's still not clear whether you (lbgrn82) are trying to run an operation against all the transaction records, or whether you are trying to set the correct price for an item in a single transaction record during data entry. These are very different things. Please clarify.

                  Feel free to send me a private message through this message board if you wish.


                  • #10
                    Hi all, it is an invoice application. The individual transactions are imported in batches via CSV but without pricing. Invoices are created every 2 weeks to include all of the individual transactions a customer makes during that time period. It's fuel products so prices change frequently but not necessarily daily. There are 10s of products, 100s of customers and 1000s of transactions for each billing period (invoice). It sounds like it might be easiest for me to create an operation that copies and pastes the previous day's prices so there will be a price for each day of year for each product and then a post operation that applies prices for the unbilled transactions?


                    • #11
                      I think you will end up with unhappy customers and a mess of trouble.
                      The "Striking Date $ Value" is essential.
                      If someone places an order for, say 100 Litres of Heating Oil, they will have looked around and established the best price available. That's the price they expect to pay.
                      If as your app suggests, they don't care, and trust you to bill whatever you want, that seems like a recipe for disaster.

                      When you get the CSV, is there a reason that no pricing information is included? I would have thought that the data entry would have captured that.
                      Or have I misunderstood?

                      You could indeed copy the previous day's prices so that each day has a price value, so that is one approach Another is to capture the daily price somehow and automate the update process. Depends on how, how and where you get the pricing info from.
                      Ted Giles
                      Example Consulting - UK

                      See our site for Alpha Support, Conversion and Upgrade.


                      • #12
                        Ok, I'll say it. I believe Ted was tending towards this. Your design is hurting yourself. Your Pricing table engenders a less than desirable filtering needed to get to the price for the transaction. I would work off the principle of one day one price and rid myself of a date range construct. There must be a daily/weekly price update, so I would transform this to one day one price model. If the table gets large, archive...
                        Mike W
                        "I rebel in at least small things to express to the world that I have not completely surrendered"


                        • #13
                          This is one of those time when mysql works so much better than dbf tables (I'm making worst case assumptions here.
                          If you are using dbf tables, there are ways to use sql without going through the nightmare of moving everything to sql,
                          provided you can dump your data into csv/txt files.
                           select t.product_id, `Date`,
                          (select q.price from pricingTable q where q.product_id = t.product_id and
                 between q.startDate and coalesce(q.endDate,curdate()) ) `Price`
                          from TransactionTable ...
                          Last edited by madtowng; 08-17-2020, 11:26 PM.
                          Gregg Schmidt


                          • #14
                            You could use the "between " test for dates in DBF's, Greg.
                            The original issue was not having a value against a date, so the last available one was needed - whenever that was.
                            I have looked at finding the last record with a value in it, but that doesn't get over the issue of missing data.

                            Given the original scenario, capturing the last value and using that WHEN there no date and value data avialable would work.
                            Ted Giles
                            Example Consulting - UK

                            See our site for Alpha Support, Conversion and Upgrade.


                            • #15
                              As far as I know, we do not have a coalesce() type function when working with dbf tables.
                              I believe coalesce() makes the code work as desired.
                              Gregg Schmidt