Tracking changes in database

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.

I think Larry is talking about this article:
Audit Trail - Log changes at the record level
at:
http://allenbrowne.com/AppAudit.html

Assuming we are talking about JET tables (not an ADP), you can create tables
in the front end and in the back end.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"tina" wrote in message
...
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


"Larry06Green" wrote in message
...
Allen Browne wrote a response called "Creating an Audit Log" in
which hestates that if the database is distributed (front-end forms,
back-end tables) the temp audit table must be local to the workstation."
Can someoneexplain 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


"Larry06Green" wrote in message
...
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.

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


"Allen Browne" wrote in message
...
I think Larry is talking about this article:
Audit Trail - Log changes at the record level
at:
http://allenbrowne.com/AppAudit.html

Assuming we are talking about JET tables (not an ADP), you can create
tables
in the front end and in the back end.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"tina" wrote in message
...
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


"Larry06Green" wrote in message
...
Allen Browne wrote a response called "Creating an Audit Log" in
which hestates that if the database is distributed (front-end forms,
back-end tables) the temp audit table must be local to the
workstation."
Can someoneexplain to me exactly how this is done? I have between
35 and 40 users accessing the database.

"tina" wrote in
:

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

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.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

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


"David W. Fenton" wrote in message
36.92...
"tina" wrote in
:

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

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.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

btw, i just noticed that i mis-spelled your name in my previous post, sorry
about that!


"tina" wrote in message
...
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


"Allen Browne" wrote in message
...
I think Larry is talking about this article:
Audit Trail - Log changes at the record level
at:
http://allenbrowne.com/AppAudit.html

Assuming we are talking about JET tables (not an ADP), you can create
tables
in the front end and in the back end.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"tina" wrote in message
...
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


"Larry06Green" wrote in
message
...
Allen Browne wrote a response called "Creating an Audit Log" in
which hestates that if the database is distributed (front-end forms,
back-end tables) the temp audit table must be local to the
workstation."
Can someoneexplain to me exactly how this is done? I have between
35 and 40 users accessing the database.