Results 1 to 8 of 8
  1. #1
    Join Date
    Apr 2009
    Posts
    67

    Unanswered: Help with this form I attached data

    I attached the data file. I have form for data entry to table and it is continuous form and every day we enter about 60 items, what I like to do is enter all the data and then have the option to save yes or no "Do you want to save yes or no". Right now when I enter information to each field it automatically gets saved to the table. How do i do this.

    Thanks
    Attached Files Attached Files

  2. #2
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    You want to add 60 items in one go before saving any of them?

    The only way I know of to do that is to allow the form to collect the data in a TEMP table and when they click "SAVE" the save command moves all the data from the TEMP table to the real one and the "CANCEL" button would simply empty the TEMP table.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    or save the data on the quiet with a flag which identifies what records have been added but not verified. and at the end of your session ask if they want to save the 60 or so rows. if they say yes clear the flag, if they say no delete'em

    theres no need for your system to neccessarily replicate the business "logic", providing the user gets what they expect then thats all they want. how you implement those requirements and manage those expectations is up to you
    I'd rather be riding on the Tiger 800 or the Norton

  4. #4
    Join Date
    Apr 2009
    Posts
    67
    Quote Originally Posted by StarTrekker
    You want to add 60 items in one go before saving any of them?

    The only way I know of to do that is to allow the form to collect the data in a TEMP table and when they click "SAVE" the save command moves all the data from the TEMP table to the real one and the "CANCEL" button would simply empty the TEMP table.
    StarTrekker,

    How do acheive this do I have to create another table, I'm new to access any your help will be appriciated.

    Thanks

  5. #5
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Quote Originally Posted by healdem
    or save the data on the quiet with a flag which identifies what records have been added but not verified. and at the end of your session ask if they want to save the 60 or so rows. if they say yes clear the flag, if they say no delete'em
    Good idea! ... Provided people aren't fussed about autonumber values jumping!

    Quote Originally Posted by hmho
    How do acheive this do I have to create another table...
    Yes. The data entry screen writes to that table. The SAVE button copies them, perhaps with an APPEND query and a DELETE query and the CANCEL button deletes them.

    Logic issue though... I really can't imagine anyone cancelling the data entry of 60 records. For that reason, I'd go with what healdem said since the CANCEL button would never really be clicked... or alternatively, don't bother and just let the records be saved normally as the user works and let them edit mistakes as they are found.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  6. #6
    Join Date
    Mar 2003
    Location
    The Bottom of The Barrel
    Posts
    6,102
    Provided Answers: 1
    Assuming there is a fantastic justification for holding open a "batch" of transactions like this, I would say go ahead and model the database to provide a "session" for the user that exists separate of the "confirmed" data.

    ie:

    Session
    ---------
    session_id
    user_id
    session_start
    session_end

    SessionBatch
    -------------
    session_batch_id
    session_id
    session_batch_start
    committed

    SessionData
    -----------
    session_batch_id
    ... temporary item data ...



    This all depends on how much work you're willing to do to control your "temporary" batches though...
    oh yeah... documentation... I have heard of that.

    *** What Do You Want In The MS Access Forum? ***

  7. #7
    Join Date
    Apr 2009
    Posts
    67
    Quote Originally Posted by StarTrekker
    Good idea! ... Provided people aren't fussed about autonumber values jumping!


    Yes. The data entry screen writes to that table. The SAVE button copies them, perhaps with an APPEND query and a DELETE query and the CANCEL button deletes them.

    Logic issue though... I really can't imagine anyone cancelling the data entry of 60 records. For that reason, I'd go with what healdem said since the CANCEL button would never really be clicked... or alternatively, don't bother and just let the records be saved normally as the user works and let them edit mistakes as they are found.
    This is the reason why i love the forum I come here with a question and I get better answer than I can ever imagined. You guys are right what I need is not temp table but the oppurtinty for the person entering the information to be able to edit as they are entering and at the end to save it. Can you please guide me how to acheive this and if there is better way to do please let me know. Thanks

  8. #8
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    The point is "why?". What is wrong with letting the system save the user's data as they go?? The data won't disappear, they can go back and correct issues they find ad hoc, and the system still saves the changes as they go. All they need to at the end is CLOSE since everything is automatically saved already.

    Apart from the "at the end to save it" part, all of what you want is the default behaviour for a continuous form.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •