Michael,
We would need more information on your overall solution architecture to give really complete answers on this kind of question.
For example:
Are you 100% MS-Access here (meaning, the data isn't stored to SQL Server or another BE database)? (SQL Server and other DBs make Triggers and other options available, as another avenue to work this issue.)
Are there perhaps more complex business rules around potential accounting issues in play? (an example may be issues surrounding bulk payments for multiple invoices over time...or, "no we indicated we wanted to pay These other invoices...not that invoice, because there an ongoing dispute over some item." - those sorts of issues which could require "unlocking and un-paying" some invoices later in time).
For a purely MS-Access approach, I'd remind you that Data Macros are available (sort of trigger-like Macros that work at the DBEngine level) that could work using a Locked flag at the record level to prevent table reads/writes depending on the logic flow implemented. (For example, are the invoice detail rows locked individually, or is the locked flag only at the invoice level? - This would affect the Data Macro designs.)
For example:
Are you 100% MS-Access here (meaning, the data isn't stored to SQL Server or another BE database)? (SQL Server and other DBs make Triggers and other options available, as another avenue to work this issue.)
Are there perhaps more complex business rules around potential accounting issues in play? (an example may be issues surrounding bulk payments for multiple invoices over time...or, "no we indicated we wanted to pay These other invoices...not that invoice, because there an ongoing dispute over some item." - those sorts of issues which could require "unlocking and un-paying" some invoices later in time).
For a purely MS-Access approach, I'd remind you that Data Macros are available (sort of trigger-like Macros that work at the DBEngine level) that could work using a Locked flag at the record level to prevent table reads/writes depending on the logic flow implemented. (For example, are the invoice detail rows locked individually, or is the locked flag only at the invoice level? - This would affect the Data Macro designs.)
Regards,
Mark B.
Mark B.
On 12/28/2025 1:20 PM EST michael simpson via groups.io <saccity101=yahoo.com@groups.io> wrote:I would like to add a lock to records once an invoice is sent out.. to prevent accidental changes.My first thought is to add a field (Lock) to each record and then add a before update procedure on each field, many of the fields also have after update procedures,Can I use both Before and After update procedures,Is there a better way to lock down records.Take care,
Mike the Plumber
Sac City Plumbing
._,_._,_
Tidak ada komentar:
Posting Komentar