April 11, 2005 at 2:13 am
As we know there is no support for triggers in MS Access.
But do u guys have any alternatives for this.
My Blog:
April 11, 2005 at 5:26 am
IF you are firing SPs have them 1st do an INSERT/UPDATE into the history table and THEN perform the request...
IF you are firing AD-HOC queries 1st perform HISTORY and THEN current (same as above)
Good Hunting!
AJ Ahrens
webmaster@kritter.net
April 12, 2005 at 1:41 am
When you talk of Access I assume that you mean JET - which is the native database engine for Access?
JET does not have Triggers (or Stored Procedures come to that) and there is no back-end mechanism to fire off any processing when data in a JET table is modified.
Of course you can use SQL Server/MSDE as a back end to an Access front end and in that scenario you can use triggers just as you would in any other SQL Server database.
Regards
David Saville
Aldex Software Ltd.
April 12, 2005 at 2:46 am
Typically in Access I'd fire trigger like code using the Form object's Before Update and/or After Update events.
Another option would be to move your database updates into a VBA function, and isolate your 'trigger' code in a transaction.
April 12, 2005 at 3:06 am
Thank you for all your ideas
My Blog:
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply