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

Using <Tbl>.enter_begin() to populate other table removes current record

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

    Using <Tbl>.enter_begin() to populate other table removes current record

    I have a table with event code called on the CanSaveRecord event to populate another table with a new record. This code does populate the other table but it removes the record that was just manually entered from the open table.Here is the code:

    ================
    CONSTANT ENTER=2
    dim tbl_mode as n
    tbl_mode=table.get("operation_summary").mode_get()
    if (tbl_mode=ENTER) then

    dim mt_num as c
    dim opcode as c
    mt_num=table.get("operation_summary").Mt_Number
    opcode=table.get("operation_summary").Op_Code

    cost_table=table.open("[pathalias.adb_path]\costs_summary")

    cost_table.enter_begin()
    cost_table.Mt_Number=mt_num
    cost_table.Op_Code=opcode
    cost_table.enter_end()
    cost_table.close()
    end if

    =================

    So again just to clarify the new record does appear in "costs_summary.dbf" however the manually entered record in "operation_summary.dbf" disappears as soon as it is entered. Is there a particular line in this code that removes that manually entered record? I'm unable to find anything that would cause the removal unless enter_begin() and enter_end() do something behind the scenes.

    #2
    Re: Using &lt;Tbl&gt;.enter_begin() to populate other table removes current record

    Matthew

    I'd suggest that you use the debug(1) command to help you with the coding.

    You have a few errors in your code and this will cause the cansave event to cancel the save of the original record.

    ie tbl_mode=table.get("operation_summary").mode_get() is not valid syntax
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      Re: Using &lt;Tbl&gt;.enter_begin() to populate other table removes current record

      That line of code does give me the correct mode of the table as far as I can tell. The function table.get(alias) gives me a table object. From there I can do <obj>.mode_get() with the table object i just received to get the table mode. It seems to be working correctly as far as I can see. What do you see that I am missing?

      The debugger progresses through the script exactly how I thought it would and correctly identified what mode the table was in.
      Last edited by Sperrrow; 06-24-2010, 09:59 AM.

      Comment


        #4
        Re: Using &lt;Tbl&gt;.enter_begin() to populate other table removes current record

        I fixed the issue by placing this code in the OnSaveRecord event.

        Comment


          #5
          Re: Using &lt;Tbl&gt;.enter_begin() to populate other table removes current record

          Originally posted by Sperrrow View Post
          I fixed the issue by placing this code in the OnSaveRecord event.
          Oops - do you mean no code? I don't see your code.
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment


            #6
            Re: Using &lt;Tbl&gt;.enter_begin() to populate other table removes current record

            Yeah I guess that would help if I posted it. I moved all of this code to OnSaveRecord:

            ================
            CONSTANT ENTER=2
            dim shared tbl_mode as n
            if (tbl_mode=ENTER) then

            dim mt_num as c
            dim opcode as c
            mt_num=table.get("operation_summary").Mt_Number
            opcode=table.get("operation_summary").Op_Code

            cost_table=table.open("[pathalias.adb_path]\costs_summary")

            cost_table.enter_begin()
            cost_table.Mt_Number=mt_num
            cost_table.Op_Code=opcode
            cost_table.enter_end()
            cost_table.close()
            end if

            =================

            Mind you I did change the variable declaration of tbl_mode to "dim shared tbl_mode as n" and also had that line in the CanSaveRecord event because I wasn't sure if you could get the table mode in OnSaveRecord.This code was left in CanSaveRecord:

            =====================
            dim shared tbl_mode as n
            tbl_mode=table.get("operation_summary").mode_get()
            =====================

            Comment


              #7
              Re: Using &lt;Tbl&gt;.enter_begin() to populate other table removes current record

              Matthew,
              Instead of constantly obtaining a new table pointer with table.get() the following is more widely used.....(changes in red).
              Code:
              [COLOR=Red]dim tbl as p[/COLOR]
              [COLOR=Red]tbl=table.get("operation_summary")[/COLOR]
              [COLOR=Red]if tbl.mode_get()="ENTER" then[/COLOR]
                  
                     dim mt_num as c
                     dim opcode as c
                     mt_num=[COLOR=Red]tbl[/COLOR].Mt_Number
                     opcode=[COLOR=Red]tbl[/COLOR].Op_Code
              
                     [COLOR=Red]dim cost_table as p[/COLOR]
                     cost_table=table.open("[pathalias.adb_path]\costs_summary")
              
                     cost_table.enter_begin()
                        cost_table.Mt_Number=mt_num
                        cost_table.Op_Code=opcode
                     cost_table.enter_end([COLOR=Red].T.[/COLOR]) [COLOR=Red]'default is .T. but like to be explicit[/COLOR]
                     cost_table.close()
              end if
              Just another way of doing it....pick and choose what works for you!! :)
              Mike
              __________________________________________
              It is only when we forget all our learning that we begin to know.
              It's not what you look at that matters, it's what you see.
              Henry David Thoreau
              __________________________________________



              Comment


                #8
                Re: Using &lt;Tbl&gt;.enter_begin() to populate other table removes current record

                Also when opening another table to enter or change records, putting a flag to use with Enter_end() allows you to trap any errors that might end the script before the table is closed.

                Code:
                dim cost_table as p
                dim commit_flag as L
                commit_flag = .t.
                on error goto ERRMSG
                cost_table=table.open("[pathalias.adb_path]\costs_summary")
                       cost_table.enter_begin()
                          cost_table.Mt_Number=mt_num
                          cost_table.Op_Code=opcode
                       cost_table.enter_end(commit_flag) 
                cost_table.close()
                end
                ERRMSG:
                commit_flag = .f.
                'add custom error msg here
                RESUME NEXT
                Robin

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                Comment

                Working...
                X