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

field rule post vs. <tbl>.post()

  • Filter
  • Time
  • Show
Clear All
new posts

  • field rule post vs. <tbl>.post()

    I have an amount field that posts(field rules) up to a cust_hdr table. This works as advertised. Even if after data entry is completely completed (ie. record is saved) you then delete the record, 'undo on delete' works as well.

    My problem:
    Insofar as field rules posting is 'real time' and does NOT actually happen after the record is saved, how do I back off a post if we cancel() out of data entry?

    Conversely, if I put the posting on the save button using xbasic, how then do I un-post a record that has been saved and is now being deleted?

    Tom C

  • #2
    RE: field rule post vs. &lt;tbl&gt;.post()


    I don't follow.

    Can you give us an example of what you're talking about? My experience with the post field rule led me to think that the posting occurs when the record in the transaction table is saved. Not before. So, I would think if the user begins an entry, but then cancels it, there would be no change in the related field in the table that's the target or destination of the post. Are you seeing something differently ? Can you show it to us ?

    -- tom


    • #3
      RE: field rule post vs. &lt;tbl&gt;.post()

      You follow perfectly.
      Your understanding was also my understanding.

      I think this is best described with an example (attached)

      First, open the default browse of tbl_custhdr and look at the value in a field named PSLS (purchases since last statement). This number is the result of a field rule post from tbl_jobsdetail->amount. Make a note of the amount and the account.

      Next, open mainmenu, press 'new install', select the previously noted account, then click on 'cancel record'

      Finally, revisit the default browse of tbl_custhdr and look again at the psls field. Your cancelled installation request actually posted an amount and did not un-post when you cancelled.

      One small item in a thankfully shrinking list of small items left to resolve before rollout.

      Thanks Tom,

      Tom C


      • #4
        RE: field rule post vs. &lt;tbl&gt;.post()

        Even though the post field rule posts an amount, the actual records are NOT in fact created or saved. That piece works as it should.
        Tom C


        • #5
          RE: field rule post vs. &lt;tbl&gt;.post()


          I am having trouble with your demo.

          Your startup form blocks access to the control panel.

          If I create a new database and attach your tables the Install button doesn't work correctly. It opens the order entry form but I get an error message that a new record is already started...

          Can you simplify this for me ?

          -- tom


          • #6
            RE: field rule post vs. &lt;tbl&gt;.post()


            I found your hotspot and can get to the control panel.

            But I've run out of time and will have to look at it later.

            -- tom


            • #7
              RE: field rule post vs. &lt;tbl&gt;.post()


              You're using a set based form to enter the new job/order record. some of the fields are from the primary table. Some of the fields are from the two child tables. When focus moves from a field in one table to a field in a second table the pending changes in the first table are saved. I think this is what's causing the post field rule to fire. Your effort to reverse or cancel the transactioin is not working completely. You're relying on referential integrity to delete the job_details record. I think this will never cause the post field rule to fire in the job_details table, since it's not working through the form's interface, it works behind the scenes, just as though you were manipulating the details table with xbasic.

              I suggest you enter the job details using a form based on the job_details table, using lookup functions to retrieve necessary field values from related tables.

              -- tom


              • #8
                RE: field rule post vs. &lt;tbl&gt;.post()

                Another issue is the use of the events on a lookup field to set values. When there is a lookup on a field, the events fire when the lookup opens and when it closes. This results in the program trying to create multiple enters. Both the current OnArrive and OnDepart code put the form in enter mode.

                The solution is to remove all of the event code from the lookup field. Use the code that opens the form to set the form in enter mode and then use the CanArrvive or OnArive for the next object to set the values you currently have on the OnDepart.

                Here is some code for the menu that will open the form on a new record.

                if is_object("frm_orderentry") then
                frm = form.load("frm_orderentry")
                end if

                If you want to test the event sequence, put something like this on every event. This will send a line to the trace window every time the event fires and will show the sequence.

                trace.writeln( "OnArrive") 'change the event name to the current event



                • #9
                  RE: field rule post vs. &lt;tbl&gt;.post()

                  I was hoping to avoid that. I've tossed your ideas into the hopper and am considering them.
                  Thanks very much for reviewing my problem.

                  Thanks for you suggestion, though, I haven't seen the problem you describe. Will keep a printed copy of your post. Thank you as well.

                  Tom C