Tracking changes in database

  • Thread starter Thread starter Larry06Green
  • Start date Start date
L

Larry06Green

Allen Browne wrote a response called "Creating an Audit Log" in which he
states that if the database is distributed (front-end forms, back-end tables)
the temp audit table must be local to the workstation." Can someone explain
to me exactly how this is done? I have between 35 and 40 users accessing the
database.
 
Larry, i hesitate to comment without being able to review the source of the
attributed statement. can you post a link to the response? and better yet,
perhaps Allen will notice this thread and respond directly.

hth
 
hi Allen, and thanks for responding. i think you're right, and the op's
question makes sense now. :)

Larry, presumably (hopefully) your database is split, with the tables in a
backend db on a server, and the other database objects, and links to the
backend tables, in a frontend db that is distributed to each user's PC. as
Allen says, the temp table should be in the frontend db, so each user's
actions don't conflict with another user's, before the audit data is written
to the permanent table in the backend db.

hth
 
as
Allen says, the temp table should be in the frontend db, so each
user's actions don't conflict with another user's
Click to expand...

Not in the front end at all! They should be in a separate temp db so
that the front end doesn't bloat unnecessarily, and so that the
audit trail is not lost when the front end is replaced with a new
version.
 
i agree that, personally, i'd place the temp table in separate, temp db to
avoid frontend bloat. but the temp data is written to the permanent audit
table in the backend, once the transaction is confirmed - if i read Allen's
webpage information correctly - so "losing the audit trail" is not a
consideration.

hth
 
Back
Top