log record change in back-end?
in [Tables]
|
From: GBA on 29 Sep 2009 13:35 is there a method, in the back-end file, to log that a value (any value) in a record was changed? - - adding a new field to the table just for this purpose is ok. I can easily see a method if one can put vba in the front-end form that the user uses. I can use vba to insert a change code into that record's log field. But I can not see any method that would exist only in the back-end file. Is there any technique out there?
From: Jeff Boyce on 29 Sep 2009 15:19 Access doesn't offer table-level 'triggers'. Have you looked into using SQL-Server or another more robust back-end? Regards Jeff Boyce Microsoft Office/Access MVP "GBA" <GBA(a)discussions.microsoft.com> wrote in message news:5672390F-0208-4E14-9C0A-70466064E614(a)microsoft.com... > is there a method, in the back-end file, to log that a value (any value) > in a > record was changed? - - adding a new field to the table just for this > purpose > is ok. > > I can easily see a method if one can put vba in the front-end form that > the > user uses. I can use vba to insert a change code into that record's log > field. > > But I can not see any method that would exist only in the back-end file. > Is > there any technique out there?
From: Jerry Whittle on 29 Sep 2009 15:26 Not with Access. If this is a hard requirement, you could upsize to something like SQL Server or Oracle. They both support auditing that can tell you who was messing with the data. They also support triggers at table level which could be used to record when a record was changed and by whom. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "GBA" wrote: > is there a method, in the back-end file, to log that a value (any value) in a > record was changed? - - adding a new field to the table just for this purpose > is ok. > > I can easily see a method if one can put vba in the front-end form that the > user uses. I can use vba to insert a change code into that record's log > field. > > But I can not see any method that would exist only in the back-end file. Is > there any technique out there?
From: GBA on 29 Sep 2009 20:58 thanks both...you confirmed my thinking. I did find however a technique to meet my current need - - - I keep a Prior copy of the back end tables...then periodically I compare the current Back End with the Prior - and can identify all changed records. And rotate the old Prior to archive, the current back end to Prior - and await the set time period for the next compare with current. Not the right solution in every situation - but works in my case..... thanks again for your input.... "Jerry Whittle" wrote: > Not with Access. > > If this is a hard requirement, you could upsize to something like SQL Server > or Oracle. They both support auditing that can tell you who was messing with > the data. They also support triggers at table level which could be used to > record when a record was changed and by whom. > -- > Jerry Whittle, Microsoft Access MVP > Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. > > > "GBA" wrote: > > > is there a method, in the back-end file, to log that a value (any value) in a > > record was changed? - - adding a new field to the table just for this purpose > > is ok. > > > > I can easily see a method if one can put vba in the front-end form that the > > user uses. I can use vba to insert a change code into that record's log > > field. > > > > But I can not see any method that would exist only in the back-end file. Is > > there any technique out there?
From: Allen Browne on 30 Sep 2009 03:29 You might like to keep an eye open for the changes proposed for Access 2010 when it is released next year. The new version will support data macros, which give you similar results to triggers. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "GBA" <GBA(a)discussions.microsoft.com> wrote in message news:6B321F36-62CF-45F5-9D3F-523A7AFC5E12(a)microsoft.com... > thanks both...you confirmed my thinking. > > I did find however a technique to meet my current need - - - I keep a > Prior > copy of the back end tables...then periodically I compare the current Back > End with the Prior - and can identify all changed records. And rotate > the > old Prior to archive, the current back end to Prior - and await the set > time > period for the next compare with current. > > Not the right solution in every situation - but works in my case..... > thanks > again for your input.... > > "Jerry Whittle" wrote: > >> Not with Access. >> >> If this is a hard requirement, you could upsize to something like SQL >> Server >> or Oracle. They both support auditing that can tell you who was messing >> with >> the data. They also support triggers at table level which could be used >> to >> record when a record was changed and by whom. >> -- >> Jerry Whittle, Microsoft Access MVP >> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. >> >> >> "GBA" wrote: >> >> > is there a method, in the back-end file, to log that a value (any >> > value) in a >> > record was changed? - - adding a new field to the table just for this >> > purpose >> > is ok. >> > >> > I can easily see a method if one can put vba in the front-end form that >> > the >> > user uses. I can use vba to insert a change code into that record's >> > log >> > field. >> > >> > But I can not see any method that would exist only in the back-end >> > file. Is >> > there any technique out there?
|
Next
|
Last
Pages: 1 2 Prev: conditional list box Next: Please Help?? Split Database - Refering to backend |