A question on Allen Browne's Audit trail procedure?

T

Tony Williams

I wanted an Audit trail on changes to a database and someone pointed me in
the direction of Allen Browne's procedure for creating an Audit log. I have
tried this and it is fantastic! However I have one small problem. In the
instructions it says this:
For each table you wish to audit, you will create two more tables, as
follows. If your database is split into two mdb files, the table created at
step 2 (temp table) must be in the code mdb (workstation file), and the
table at step 5 (main audit table)in the data mdb (server file.)

I have my database split into Front End and back end and I created the main
audit table in the backend database. However it doesn't show in the list of
linked tables in the Front end database and when the routine runs it says it
can't find the table. If I move the table to the Front end it runs OK but
that means it wont pick up any other users as it's on the local machine.

How do I get the Front End to recognise and find the main audit table in the
back end database?

Again great procedure for anyone who wants to keep track of edits.

Thanks
Tony
 
D

Douglas J. Steele

You have to link the new table(s) to the front-end (under File | Get
External Data | Link Tables)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top