[AccessD] Audit Trail Suggestions

John W. Colby jwcolby at gmail.com
Sat Mar 14 21:23:03 CDT 2015


Ahh so he did.  :(

John W. Colby

On 3/14/2015 6:15 PM, Stuart McLachlan wrote:
> Dave actually stipulated SQL Server 2008 R2 as the BE, but most responder appear to have
> missed that.   :(
>
> On 14 Mar 2015 at 12:59, Arthur Fuller wrote:
>
>> 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
>
>



More information about the AccessD mailing list