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

Contrasting Append and Lookup

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

    Contrasting Append and Lookup

    I think it is safe to say that the append operation and database lookup function both are ways to move record info from one table to another. It seems to me that the using a lookup is always a smooth and quick operation, whereas, I have had trouble reliably using the append operation and it can be slow even appending one record (compared to data that is moved with a lookup). The append operation appears to slow in a multi-user enviroment as it has to lock and ulock the table.

    Are these two operations as similar as I think? Does Alpha "mechanically" treat them the same?

    I have a mission critical application that we haved used in our business for 5 years that uses append operations to move data from a sales order table to a workorder table (with additional fields added, like date, etc.). It has always operated slowly.

    Any thoughts?

    Thanks,

    Don

    #2
    Re: Contrasting Append and Lookup

    An append operation adds records to a table based on some design. I fail to see how a lookup does anything similar. Could you elaborate?
    There can be only one.

    Comment


      #3
      Re: Contrasting Append and Lookup

      Stan,

      I was thinking that when a lookup is performed, we select data from one table (the lookup source) and then once selected, it is "appended" or copied into the table we are filling in.

      In an append operation, we are copying records or select data from one table based on some criteria, into another table.

      Seems like the operations of each are similar.

      I realize that these are different operations used for different purposes, but it seems like they function similarly. Again, I am curious because true append operations seem to be slow due to table locking and unlocking, while lookup seems to be a similar process that moves quickly.

      I apologize if I am not making sense.

      Thanks,

      Don

      Comment


        #4
        Re: Contrasting Append and Lookup

        Making sense but I don't see them as equal. The append operation, especially a unique records only, has to evaluate the records in the master table, evaluate the records in the transaction table, decide if the first record in the transaction table is unique, append it, add it to the list of master table records against which to check the next transaction record, and in a multi-user situation, possibly reevaluate the records in the master table if a new record has been added or changed, then repeat.

        A lookup is only working on one record, one field, and changing its value.

        Unless I misunderstand your meaning, which is not at all unusual.
        There can be only one.

        Comment


          #5
          Re: Contrasting Append and Lookup

          Stan,

          I see I am over simplifying the append operation, as the end result of data moving from one place to another is the only thing that is similar between the append and the lookup.

          I am using append operations to move 1 record at a time from a sales order form to a workorder form while adding additional information. When the Production Manager wishes to prepare a work order for the day, he appends data from the sales order, while automatically adding aditional data such as made date, pcs produced, etc. Works well, but the append can be slow.

          Thinking that if I understood the "mechanics" of how the lookup moved data, I could apply to my situation and not use the append operation.

          Don

          Comment


            #6
            Re: Contrasting Append and Lookup

            No problem. Should be easy to help you construct a small script which would

            read the values from the sales order form
            open the work order table
            create a new record there
            populate the new record with the values from the sales order
            populate the new record with aditional data such as made date, pcs produced

            This script should execute "instantaneously".

            An alternative might be to delve into marking records. If all records in the sales order table are initially unmarked, you mark the record while in the sales order form, change the append operation to operate on marked records, it should process exceedingly quickly.

            How many people are using the feature of transferring records from sales order to work order?
            There can be only one.

            Comment


              #7
              Re: Contrasting Append and Lookup

              Stan,

              Thanks for your response. The script that you detail is exactly the process that I am using. I have tried the marking technique you suggest, but found that if for any reason the record is not unmarked, obviously there was trouble. I still mark and unmark the record so there is a visual action on the screen when a record is selected to be appended, but the actual append operation is based on a unique serial number.

              Each record in the Sales Order table has a unique serial number. There is a button on the sales order screen that grabs the serial number of the current record, and then the following script is run:

              :Pick_off_Production_Ord:BROWSE1.activate()
              :Pick_off_Production_Ord:Tables:PRODUCTION_ORDER_DETAIL.change_begin(HONOR_FIELD_RULES)
              :Pick_off_Production_Ord:Tables:PRODUCTION_ORDER_DETAIL.mark()
              :Pick_off_Production_Ord:Tables:PRODUCTION_ORDER_DETAIL.change_end(.t.)
              :Append.run_silent("Append Workorder")
              :Pick_off_Production_Ord:Tables:PRODUCTION_ORDER_DETAIL.change_begin(HONOR_FIELD_RULES)
              :Pick_off_Production_Ord:Tables:PRODUCTION_ORDER_DETAIL.unmark()
              :Pick_off_Production_Ord:Tables:PRODUCTION_ORDER_DETAIL.change_end(.t.)


              The append operation then finds the matching record (by serial number) in the sales order table and then appends the information to the workorder table.

              Please note that the sales order and workorder sets are about 10 tables deep.

              Don

              Comment

              Working...
              X