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

Posting

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

  • Posting

    We want to post from a field "price" in the line item.dbf to a field "total_billed" in the customer dbf.

    The problem is the linking keys. Customer.dbf has a customer_id field. The line_items.dbf has an invoice_number field. So, there is no matching linking key values. I tried adding a customer_id field to the transacton dbf but it did not work.

    Also, what is the procedure for adding a "posted" logical field to the transaction dbf? I know how to add it to the dbf structure, but from there I am lost.

    I would sure like an example of the above.

    We are modifying the invoice.dbf included with A5V4.5.

  • #2
    RE: Posting

    James,

    It almost sounds like you need to 'post' the transaction detail item to the invoices record (to create an invoice total), and then use another post from the invoice total field to the customer record. I've never attempted a two layer post like that but that's the direction I'd explore if I were you.

    -- tom

    Comment


    • #3
      RE: Posting

      Tom, this would seem a required process in every accounting application. In a previous message you advised that it is properly handled by an Xbasic script. What I really wanted to post was the invoice total, that is to include line item totals as well as tax and shipping, to another dbf file to compare payments and invoice totals for a customer. I assume the new add on apps for Ver 5 has this outlined.

      We are not quite ready to jump into Version 5. Maybe someone has this written that I could look at.

      I am posting payments made for a customer, but not for individual invoices, and that works pretty well. Here again I have not constructed the posted logical field in the transaction database. I assume this is a necessary part to keep from reposting or is that only a concern when the post operation is constructed in the post card and not the field rules.

      I hope I am not belaboring a subject that all programmers know how to handle.

      Comment


      • #4
        RE: Posting

        James, as noted previously, the post field rule and the saved post operation have distinctly different scopes.

        The post field rule adds, substracts, or replaces the field value from the current record only. If there are related records present in the 'transaction' table their field values are NOT added to, subtracted from, or substituted for values in the target fields of the 'master' table.

        In sharp contrast, a saved post operation examines each and every record of the 'transaction' table. If a record in the 'transaction' table meets the current filter criteria field values from that record are posted to a 'master' table. Then the next record in the transaction table is fetched, examined, and posted (or skipped if the filter criteria is not met). Then the next record in the transaction table is fetched, examined, and posted (or skipped)... this continues until all records in the transaction table have been processed.

        The field rule and the operation are designed to do the same thing, but for different ranges of 'transaction' records.

        I hope this clarifies things for you.

        -- tom

        Comment


        • #5
          RE: Posting

          That certainly helps.

          If a logical field "posted" is included in the transaction table how does one automatically set the value to "true" after that particular post? I assume this is necessary in either posting scenario.

          Jim

          Comment


          • #6
            RE: Posting

            James:

            Here's a very rudementary example that - with field rule events

            1. gets the Customer ID and the date into the line items.
            2. posts the line item charge into the customers 'charges' field.

            As I see it, you'd want the sales tax calculated and as part of the line-item detail. Thus, the tax and price extension can be posted to the customer record via add/post field rules linking on the customer Id. Automatically Alpha will keep track of subsequent changes made after the save and adjust that balance properly.

            Shipping charges could be posted from the header using the customer id linking common fields.

            On the other hand, as Tom suggests, you can get the invoice total into the header record and post only that amount to the customer's 'charges' field.

            I'm sure others have even better examples - this is just my humble submission.

            Ken

            Comment


            • #7
              RE: Posting

              James, your assumption is wrong. It's needed only in the saved POST OPERATION. The FIELD RULE post is activated only when you enter a new record or change the field value, as explained in the manual. You would not want to place a flag in the record which prevents further posts if the user changes the field value, I should think.

              I sent you a complete working example 8/24/02, demonstrating the saved post operation in action, including updates to a logical 'posted' field. Sounds like you missed it or haven't looked at it. I also posted it in the Code Archive for everyone else.

              Check Forum List
              Open Code Archive
              Click on Saved Post Operation Example

              -- tom

              Comment


              • #8
                RE: Posting

                Tom,

                Here is a question I have not seen answered in the past, although I'm sure someone must have run across it. It relates to this Post problem. If, for example, one creates a post on an amount in one database to update another, based on a condition, then what happens when that condition is later modified? In my current .dbf the post does nothing, because the Post is based on the amount, not the condition. But shouldn't A5 see this as a change and undo the previous input, then correct it?

                Let's say that DBF1 has one field which is "RunningAmount". DBF2 has two fields, one called "Amount" and one called "Type". If you set up the Post operation to post the "Amount" from DBF2 to "RunningAmount" in DBF1 on the condition that "Type" = Good, then the post will work on first entry or on any change to the "Amount" field. But if a correction needs to be made and "Type" now equals "Bad" then the Post does not reverse itself.

                Any ideas on this or somewhere I could look?

                Thanks as always.

                Charlie

                Comment


                • #9
                  RE: Posting

                  Charles,

                  please reframe your question. This thread deals with both field rule posts, which deal with one record at a time... and saved post operations, which deal with the entire table. I cannot tell which you are referring to in your question.

                  -- tom

                  Comment


                  • #10
                    RE: Posting

                    Tom,

                    What I am referring to is field posts. I solved the problem late last night, by using a crossadd of the dbf along with a general post to the file. Thus, each time I make any kind of change to the file, I am assured that - no matter what - I am updated fully in the other file.

                    My comment is, that it's too bad that this cannot be done within the field post. It seems though that this method, which I never use and always stay away from, because of data integrity, would only be good in the one example you mentioned, which was a checkbook update.

                    Anyway - get to bed! 4:30am is way past your bedtime!!!

                    Charlie

                    Comment

                    Working...
                    X