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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Suggestions For Multi Data Entry

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Suggestions For Multi Data Entry

    I have created a very nice ORDER ENTRY table that has all the bells and whistles that the operator will need to answer any of the customers questions. However, I have run in a problem and would appreciate any suggestions.

    This is ONE table that possibly may have 4 operators entering data at the same time. That means that all the data is going to get combined into this same table and the orders will not be correct. Am I going to have to duplicate this table for every computer (to isolate information) or is there any trick that I can do?

    Thanks
    Tags: None
    #2
    RE: Suggestions For Multi Data Entry

    Philip,

    I'm not sure what you mean by "data is going to get combined".

    If you are concerned about sequential and unique order numbers, you will need some code to "grab" the next available order number as the order begins, then reserve this order number while the order is entered, then save the order to this order number.

    In a point of sale program I wrote, I find the last record in the "order number" table, increment it, save a record with the new order number(at this point the next user cannot have the same "next" order number), save the order number to a variable, process the order, locate the record with the order number stored in the variable, save the details ("change all the record fields except the order number")of the order to this record.

    Clumsy but effective for rapid multiple data entry.


    Stan
    There can be only one.

    Comment

      #3
      RE: Suggestions For Multi Data Entry

      "DATA COMBINED"...when the operators take orders they can be entering as many as 200 items per order. All they are doing is entering quantities next to the ITEM number. These items and qty's are then appended to another table and the Order entry table is zeroed out and ready for the next order. If operator 2 starts entering while operator 1 is still entering qty's then the two orders are being combined. Is this clear as mud...?

      Comment

        #4
        RE: Suggestions For Multi Data Entry

        Without discussing your design decisions, I cannot see a way that you can avoid having an order entry table specific to each order enterer.

        I would be glad to elaborate further on my "take" on order entry, concurrent inventory adjustment, transaction record keeping, payment recording, items sold history recording, etc., but it seems you have these issues in hand.
        There can be only one.

        Comment

          #5
          RE: Suggestions For Multi Data Entry

          Philip, I'm not sure you have a problem until you 'zero out' the order entry table.

          It's my understanding that two or more operators can add records to a single table contemporaneously. If Alpha Five is busy saving the first record when the second operator tries to save, an error will occur which can be trapped and dealt with. Check out the discussion of Rolling Back Enter and Change Operations on pg 68 of the Xbasic Ref. Manual.

          I'm not certain what effects will occur when you 'zero out' the table after appending its record to others in your system. The potential for interference with other contemporaneous data entry seems large.

          Have you considered capturing the order entry data in a series of variables instead of an order entry table? The values in the variables could be blanked out after you copy them to new records added to other tables in your system.

          -- tom

          Comment

            #6
            RE: Suggestions For Multi Data Entry

            are several operators entering data to the exact same order, or are they each entering data to different orders?
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment

              #7
              RE: Suggestions For Multi Data Entry

              They would be entering DIFFERENT orders. There is the problem. Order 1 being combined with order 2 and when the append is done the two orders would be combined. I am trying to prevent this from happening. The only way I can see is to have each of the 4 computers with its own PRIVATE order entry table. Yes/No

              Comment

                #8
                RE: Suggestions For Multi Data Entry

                Phillp, I may be all wet on this one. I use a header with a control
                number that alpha assigns and the items a link by that control number.
                This keeps them from getting mixed up.


                nick

                Comment

                  #9
                  RE: Suggestions For Multi Data Entry

                  I second this option. I also create invoice headers, that must be saved, before you can bill any details. I bill as the work progresses, and close the bill out by dating it. Only invoice headers with no date can have detail added. Works like a charm.

                  Anyway - it would seem to me this would be the natural solution.

                  Stephen Williams

                  Comment

                    #10
                    RE: Suggestions For Multi Data Entry

                    I think what is happening here is that there is one order table with items, prices, etc, and a quantity ordered field. The approach taken to enter an order is that this table is opened and the and a quantity ordered field is entered. (Read post #3). This information, when the order is completely entered, is appended to another table.

                    Thus the problem of combined orders due to multiple data entry.
                    There can be only one.

                    Comment

                      #11
                      RE: Suggestions For Multi Data Entry

                      Stan,
                      You hit the nail right on the head. Any ideas how to get around the problem?

                      Thanks

                      Comment

                        #12
                        RE: Suggestions For Multi Data Entry

                        Philip,

                        Yours is really a design problem. How about copying the master order entry table (duplicating the table) to the local machine. This could be done to begin each order, at the start of each day, or when the table needs modification.

                        You might also consider adding some fields to the order entry table. Fields like ordqty1, ordqty2, ordqty3, ....

                        The enterer would be assigned a number 1, 2, ...

                        The form would display (contitionally) only the entry fields for the operator number as logged into the system.

                        The append process would only touch the info in the order entry fields for the current operator number.

                        If you don't like these, at least they may ring some bells for you.

                        Stan
                        There can be only one.

                        Comment

                          #13
                          RE: Suggestions For Multi Data Entry

                          You have given me some ideas, now the creative juices will have to work to see what method will be the best.

                          Thanks

                          Comment

                            #14
                            RE: Suggestions For Multi Data Entry

                            Have each user
                            1) enter the new order's minimal info (like customer id)
                            2) save the order
                            3) put in all the other info in change mode
                            The chances that more than one person will be in enter mode at the same time should be minimal.

                            Comment

                            Previous template Next
                            Working...
                            X