[AccessD] Audit Trail Suggestions

[David Emerson]

Thanks you everyone for your responses - plenty to work my way through.

Arthur, not sure if your comment was directed at my original question (because you didn't include the post you were responding to) but the BE is SQL 2008.

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Sunday, 15 March 2015 6:00 a.m.
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Audit Trail Suggestions

With all due respect, I have always lived by, and continue to survive by, the simple maxim that anything the database *can *do, the database *should* do. Given an Access BE, I realize that is not an immediate help, but it the bigger picture it ought to provoke the question, "Why an Access BE, when abundant free alternatives are available?"

Event-logging can and should be done in the BE The technology is all there and you can tap into it at will; and speaking from experience, they can do it better than I.

Two suggestions, therefore:

a) lose any and all Access BEs on all your projects, and replace them with any one of SQL Express, MySQL, MariaDB or PostGres;

b) put all this logic into the SQL engine of your choice, but most definitely keep it out of your FE! No single error in database-implementation is more serious than this.

A.
?
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com