Database triggers?

  • Thread starter Thread starter J S
  • Start date Start date
J

J S

In a oracle database you can create a "database trigger" which is basically
code that will be automatically executed when certain events occur like a
row being inserted into a table. I was wondering is there something similiar
in access?

I don't want a trigger that is form based. I want it to be table-based. so
that even if I'm inserting rows from a procedure the trigger will still run.
Is this possible?

-J
 
This is not possible with the storage engine in Access (JET).

Access 2000 and later allow you to use the MSDE instead.
It's essentially a throttled version of SQL Server which does support
triggers.
 
Sorry, not in Access. Remember that Access (JET actually) has the desktop
heritage, not a database server heritage.

It is available in MS-SQL Server which more of the equivalent to Oracle.

Of course, the license fee for Oracle (and MS-SQL Server) is much more than
JET so you can't expect JET to provide the same features.
 
Yes, you can most certainly use database triggers. This is especially so if
you are making a adp project.

It really depends on what database engine you are using with ms\-access. The
office cd comes with two database engines, and the 2nd choice of MSDE does
support triggers.
 
Then why is MSDE second choice?

Albert D. Kallal said:
Yes, you can most certainly use database triggers. This is especially so if
you are making a adp project.

It really depends on what database engine you are using with ms\-access. The
office cd comes with two database engines, and the 2nd choice of MSDE does
support triggers.


--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.attcanada.net/~kallal.msn
Click to expand...
 
Henro said:
Then why is MSDE second choice?
Click to expand...

Probably because earlier versions of ms-access did not ship with the MSDE.
Only the last 3 versions of ms-access have shipped with the MSDE (so,
really, only the last 3 versions of ms-access did support triggers). So, if
one is upgrading from a earlier version of ms-access, then to maintain
compatibility, the likely choice would be to use JET.

On the other hand, it was me who said the msde is the 2nd choice, and this
is not some official point of view! So, really, I can't say with any
authority that the MSDE is really the 2nd choice. It certainly is *my* 2nd
choice, but I can't really say it is the official 2nd choice! You have been
free to choose either engine for the last three versions of ms-access, and I
can't say using one engine is really a second choice!
 
Henro said:
Then why is MSDE second choice?
Click to expand...

It is second choice for a number of reasons, in a number of situations, but
might be a better choice than Access with Jet, in other situations.

It second choice because is not the default database engine for Access, and
thus, is not automatically installed and available; you are no longer
developing an "Access database" but an Access client application to a server
database (and that takes a different approach, and is somewhat more time and
effort); it does not include the very useful administrative tools that its
parent, MS SQL Server, includes.

It is first choice (only if finances preclude using MS SQL Server, and the
Developer Edition of MS SQL Server has now been significantly reduced in
price) if you need a client-server environment for a modest number of users.
A specific situation of this kind would be shared tables that must be
accessed by a modest number of clients across a slow WAN.

Larry Linson
Microsoft Access MVP
 
Back
Top