Results 1 to 5 of 5
  1. #1
    lathander is offline Novice
    Windows 10 Access 2016
    Join Date
    Mar 2020
    Posts
    5

    Update-able transactions in Access database

    What feature can we use to keep track of on-going transactions within a database, which can be updated at a later date? For example, I have an Inventory database that has a Purchase Order sheet. I want to be able to immediately input the PO data after I make the order, as a record that the transaction has been made, but not have the number of items added to the Inventory table until the goods are received, perhaps using something like a PO status (received/pending), which can be edited after the items arrived.

    Thanks in advance.

  2. #2
    Ajax is offline VIP
    Windows 10 Access 2010 32bit
    Join Date
    Mar 2015
    Posts
    8,575
    perhaps using something like a PO status (received/pending), which can be edited after the items arrived.
    that is most likely what I would do - but have the field as 'ReceivedDate'. If null, not received. You may have other fields like order date, due date to provide a sense of when expected to be received

  3. #3
    lathander is offline Novice
    Windows 10 Access 2016
    Join Date
    Mar 2020
    Posts
    5
    Yes, for the Purchase Forms, I have OrderDate, ItemID, Item amount, Vendor, and Status (may be changed to ReceivedDate). I'm just not sure how to set the PO (table/form?) so that the Item amount is not added to the Inventory table until the goods are received.

  4. #4
    Ajax is offline VIP
    Windows 10 Access 2010 32bit
    Join Date
    Mar 2015
    Posts
    8,575
    the Item amount is not added to the Inventory table until the goods are received

    by excluding those records where receivedate is null or to only include records where receivedate is not null

  5. #5
    Micron is offline Virtually Inert Person
    Windows 10 Access 2016
    Join Date
    Jun 2014
    Location
    Ontario, Canada
    Posts
    7,357
    AFAIC tblPO is for PO header data only - PO id, CreateDate, Dept, Creator, Supplier, etc.
    PO line items belong in their own table and the received status could be there. However, line items may not all come in at once so you could have a status field with a value for every item record. You might also incorporate tblInvTransactions where you track inventory transactions and not try to calculate stock quantities from PO lines if that is the intent.
    - "doesn't work" doesn't help. Implement changes in copies of your database.
    "Everyone has a photographic memory; some just don't have film." Steven Wright

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 2
    Last Post: 06-21-2018, 03:16 AM
  2. Replies: 1
    Last Post: 03-26-2016, 06:42 AM
  3. Replies: 4
    Last Post: 10-10-2015, 05:09 PM
  4. Access error 2074 - transactions
    By John_G in forum Access
    Replies: 4
    Last Post: 11-15-2011, 12:40 PM
  5. Design multi user database - avoid simultaneity transactions
    By snoopy2003 in forum Database Design
    Replies: 2
    Last Post: 02-27-2011, 12:03 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums - Senior Forums