Edward Zuris
edzedz at comcast.net
Fri Nov 30 09:44:04 CST 2012
Thanks for all the ideas.
I'll think I'll try out Access 2010 (aka Access 14)
The client is using Access 2003 on a application that
is beyond huge it is a monster that yours truly has
created.
Trying to find the VBA routine that made this or that
change to the data in a field has become a real challenge.
I have taken to creating fields where information is
changed into a field saying that Routine X, or Y did
this update. However, at the end of a test run you
find out about that the last routine to touch the data.
It would be nice in the debug mode that a flag would
be raised saying the data just changed in field X.
Once again thanks for the ideas.
Sincerely,
Ed Zuris.
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Thursday, November 29, 2012 10:22 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Event Flag or Error Flag with Data Change
Thanks Stuart,
Good to know there is 'something' there if I ever need it. I did use
triggers in SQL server a lot back in the day and they were awesome.
Cheers
Darryl
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Friday, 30 November 2012 4:10 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Event Flag or Error Flag with Data Change
Yes, same concept - but not nearly as powerful.
The table macros are failry limited in what you can do and the design
interface is a POS.
;-{
--
Stuart
On 30 Nov 2012 at 3:44, Darryl Collins wrote:
> From what I understand it is a similar concept to triggers in SQL
> Server. But I haven't had the need to play around with that
> functionality in A2010 my current role so I have zip experience of
> them. But it all sounds very promising.
>
> Cheers
> Darryl
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart
> McLachlan
> Sent: Friday, 30 November 2012 2:18 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Event Flag or Error Flag with Data Change
>
> That's the whole point of Access 2010's Table Macros.
>
> Any relevant change to the data in the table automagically triggers the
defined macro.
>
> They have removed the requirement to externally monitor the tables
changes.
>
> --
> Stuart
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com