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 Script Problems

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

    Posting Script Problems

    I have 2 posting codes on a Payroll form. I copied these from another set in which they work fine (on the form's "save" button and CanChange events).
    First one is attached to "Save" button on form:

    dim hdr as p
    sys_send_keys("{F9}")
    hdr=table.current()
    hdr.change_begin(HONOR_FIELD_RULES)
    hdr.GROSS=gross.value
    hdr.NET=field1.value
    hdr.change_end(.t.)

    dim fund as p
    dim code as c
    dim total as n
    dim tbl as p
    dim rec as n

    tbl=table.get("payroll")
    code=tbl.fund_code
    total=tbl.gross+tbl.bdgt_ded1+tbl.bdgt_ded2
    fund=table.open("fund")
    fund.index_primary_put("code")
    rec=fund.fetch_find(code)
    if rec

    #2
    RE: Posting Script Problems

    Deep stuff.

    I'd put a:

    ui_msg_box ("No matching fund code entry found for",code,UI_STOP_SYMBOL)

    in the second script like you have in the first to see if the script is firing, but not finding any matching entries. I see differences in the "setup part of the code where you open and get table names and pointers, but I don't follow them on first examination.
    There can be only one.

    Comment


      #3
      RE: Posting Script Problems

      Becky,

      Why don't you put the debugger on the second script to see what the values of the variables are and where it is going wrong.

      Bill
      Bill Hanigsberg

      Comment


        #4
        RE: Posting Script Problems

        I did try the debugger on the second script (I hope I did it correctly) and did find one field name I'd misspelled. I corrected it but am still getting haywire results.

        If I take the second script off of the form, enter a new record and press the "Save" button (with the first script attached), the correct amount posts.

        If I put the second script back on the CanChange event, enter an identical new record and press the "Save" button, some wrong amount posts (sometimes it's close, sometimes WAY off - Can't find a rhyme or reason to the amount). This is a NEW record, not an existing record which is being changed.

        I've run a database compact, update indexes often. I'm about ready to throw in the towel!

        Comment


          #5
          RE: Posting Script Problems

          Becky,

          This is just a stab in the dark since I haven't looked at your application, but why is the second script attached to the *can*-change event. This event fires *before* the form's control is edited. It seems to me that at that moment you would not yet have your new field value which could explain the erratic results. Perhaps someone will check my logic on this.

          Of course, even if valid, this analysis leaves unanwsered the question of why the code worked in its initial location.

          Bill
          Bill Hanigsberg

          Comment


            #6
            RE: Posting Script Problems

            Becky and Bill,

            I have not looked at the app yet, but I agree with Bill the script should be attached to the onchange event instead of canchange event.

            Daryl

            Comment


              #7
              RE: Posting Script Problems

              In my app for posting, I use the onsaverecord event and the onchangerecord event at the table level. It works great!

              Daryl

              Comment


                #8
                RE: Posting Script Problems

                Becky;

                By chance are you supporting direct deposit in your payroll system? If so, perhaps we can exchange ideas on prenotes, etc.

                Regards,

                Michael

                Comment


                  #9
                  RE: Posting Script Problems

                  I initially attached the codes to my parent table's OnSaveRecord and OnChangeRecord events in the field rules (see my initial question under observations, please). Neither worked there - perhaps because of the code I had attached to my form's Save button which was manipulating the table (???). Anyway, putting them on the form seemed like the next logical thing to try. By adding the first code to my Save button, I at least got that to work. I know that the CanChange event is not the best choice, but there is no OnChange event on the form, and as I stated earlier, I can't get it to work in the field rules (although I'd LIKE to!).

                  I guess what I'd like to know is: how DO I get the second code to work from the OnChange event. Am I putting the (HONOR_FIELD_RULES) in the worng place on my first script? Any other suggestions? I think the first few lines of my first script (attached to the form's Save button) are throwing the monkey wrench in the works, but I need to have them. And, as I said, they are working in another set (??)

                  Comment


                    #10
                    RE: Posting Script Problems

                    Sorry Michael,
                    The payroll part of my app is a no-frills component of a larger department management system (no direct deposits here). It's a very minor element causing a MAJOR headache right now!

                    Comment


                      #11
                      RE: Posting Script Problems

                      you REALLY don't want to put a posting script on a CanChange event. the script will fire every time you start edting any value in the record.

                      i looked at your sample files, but could not run them because of an error message when opening the payroll form:

                      bdgt_ded2 not found.

                      Comment

                      Working...
                      X