Jim Dettman
jimdettman at verizon.net
Mon Sep 26 12:31:08 CDT 2011
I wasn't even aware that feature was in there, but it's hardly what one would call transaction logging. And again, as you said, it's through macro's (and hence the UI and not at engine level). Big yawn as far as I'm concerned. I've had a system log table since day one working with Access. >From my viewpoint, it's just one more feature that doesn't need to be there. <<And, by the way, that gives you insight into how MSFT is really moving away from VBA.>> And anybody that thinks their not is crazy, but it will be a very long time in coming. The big reason at present for the push to macros is the ability to run Access apps with SharePoint. And if you've seen where Win8 is heading and Metro apps, your not going to find VBA in there at all. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms Sent: Monday, September 26, 2011 11:05 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] MS Access with IIS Re: "I'm not sure what Mark is referring to as transaction logging,but there is none that I'm aware of.." http://www.databasedev.co.uk/whats_new_in_microsoft_access_2010.html Granted, it's not the best of implementations as this feature is only enabled using the macro facility....VBA not supported. And, by the way, that gives you insight into how MSFT is really moving away from VBA. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com