[AccessD] Audit Trail Suggestions

John W. Colby jwcolby at gmail.com
Sat Mar 14 21:20:46 CDT 2015


LOL.  Arthur the sad fact is that there are a TON of apps out there in a 
TON of companies who use ACCESS as the BE.

I left Connecticut and the company for whome I wrote a call center app 
in 2006.  I wrote this app from the ground up starting in 2003 and SQl 
Server was not an option back then.  Once it was, I was not given 
permission to perform the migration.  I was telling them this whole time 
"move it to SQL Server".  THIS YEAR, I got an email from my old buddy 
John informing me that they had FINALLY migrated the app to SQL Server.

So Poo Poo all you want old buddy.  If you are elbow deep in an app and 
a company clinging for dear life to the Access BE, you do what you gotta 
do, and that is when "my class" works, neatly, cleanly and easily.

John W. Colby

On 3/14/2015 5:28 PM, Arthur Fuller wrote:
> Not in the slightest to poo-poo your most significant contributions to the
> Access community, but your class is of interest only to the (perhaps large)
> number of users who still use Access as the BE in their app of interest.
> We've traversed this path many times, and the clear result is that this is
> the wrong way to design and build apps, unless said app is really trivial,
> meaning fewer than 20 tables.
>
> As for me, I'm concerned with databases comprising 100+ tables. Now and
> then, for some friend, I will knock off a simple (less than 20 tables)
> solution, but that's not my zone of comfort. I prefer complex situations.
> I've done more than a few that involve 500+ tables. That's my comfort zone,
> and where I can bring some knowledge and experience to the table.
>
> Admittedly, these apps are infrequent, but they are the ones that I hold
> out for. The really tough problems are the ones I love: gene-analysis, and
> so on. Way back when, I coined an abbreviation, YAFOES, which means Yet
> Another Forking Order Entry System. No matter how much money you're
> prepared to toss my way, I am most emphatically not interested in such a
> gig. Call me uppity if you wish, but at my age and my level of experience,
> I choose not to travel down that familiar path. I have in mind much larger
> problems, with much larger implications for the world at large.
>
> I want to figure out how to deal with the problem of kids on the street,
> whose parents have discarded them because they declared themselves LGBT or
> whatever. That's just one example. Also include the victims of domestic
> assault, and the very limited number of shelters they can turn to, and the
> shame they feel that prevents them from turning to such a shelter for help.
>
> These are not, I realize, problems that Access developers typically
> encounter in one day's work. But I've been in this game for a long time,
> and now that I'm semi-retired, these issues have become of paramount
> importance. I have volunteered to work for several organizations whose
> mission pertains to this topic.
>
> So it may be that for the next little while I won't be able to respond
> immediately to messages posted here to me.
>
> Right now, it's time to go there.
>
> On Sat, Mar 14, 2015 at 4:44 PM, John W. Colby <jwcolby at gmail.com> wrote:
>
>> I wrote a class set to handle this.  Feed in the control to the class and
>> then watch the events.  Log changes.
>>
>> John W. Colby
>>
>>
>> On 3/14/2015 12:21 AM, David Emerson wrote:
>>
>>> Hi Team,
>>>
>>> Looking for ideas for implementation.
>>>



More information about the AccessD mailing list