See his code here

http://www.everythingaccess.com/tuto...an-Audit-Trail

Anyone using it?

Can you tell me how much this slows down the process from the end user
perspective?

How difficult did you find it to install? Debug?

Bob

On 3/7/2011 3:29 PM, BobAlston wrote:

anyone using this code???

No, I have not used that code, Bob, but I know Allen personally and from
observing his work. He definitely "knows his stuff about Access" and it
would be well worth giving it a try -- I am 100% sure that I couldn't "start
from scratch" and hope to do something better on my first few tries.

My needs for recoverability were generally taken care of by using a server
database, such as Informix, MS SQL Server, or one of the Sybase offerings as
the back end. In other cases, the only data requiring "logging" was just a
couple of tables and I'd already done those DBs before Allen published his
article.

If you are using a recent version of Access, you might consider using the
Express Edition of MS SQL Server as the data store... I believe it includes
logging and recoverability features.

Larry Linson
Microsoft Office Access MVP

"BobAlston" <bobalston9 (AT) yahoo (DOT) com> wrote

"Access Developer" <accdevel (AT) gmail (DOT) com> wrote in
news:8tpr7jFf1sU1 (AT) mid (DOT) individual.net:

But that's not even close to the same thing as an audit trail. If
Bob is using Allen's code to have a backup, a server db might be
sufficient (though there's nothing magic about it -- you still need
to do daily backups of the server database), but it might not.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

I hope I did not imply that "using a server DB" meant you'd have to do
nothing. Though, since my clients tended to have full-time DBAs and
full-time IT staffs, that was largely the case when I used it, because
backup/recovery procedures were already in place.

And, with a copy of every update, it would seem that could _expedite_, if
not provide, an audit trail.

But, the applications on which I worked were not "essentially financial" and
did not have an "audit trail requirement". I suspect, had we had one, it
would have sometimes been helpful in diagnosing and correcting errors.

Larry Linson
Microsoft Office Access MVP


"David-W-Fenton" <NoEmail (AT) SeeSignature (DOT) invalid> wrote

"Access Developer" <accdevel (AT) gmail (DOT) com> wrote in
news:8tq1mlF22rU1 (AT) mid (DOT) individual.net:

Restoring a server database from a backup is not a simple task. You
don't get a choice to restore one table or another so far as I'm
aware, so it really isn't anything close to providing a record of
what has happened.

If you need an audit trail, use Allen's code. It is an issue
entirely separate from backups.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

I've been using this code on a db for about 3 years. It works as advertized and doesn't appear to slow down the database.

I'm currently trying to set this up in a new database that is accessing tables stored in SharePoint. I'm pretty sure I won't be able to get it to work as SharePoint adds Multi-Value fields to any table that you export there.