Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Microsoft Access > Handle Triggers...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 9 Topic 29944 of 31576
Post > Topic >>

Handle Triggers in MS Access 2003 with SQL Server as Back-End

by "Ben" <pillars4@[EMAIL PROTECTED] > Apr 12, 2008 at 10:37 PM

Hi!

I have a trigger created for Customer table.  My front-end is access. 
What 
is the best approach to handle a trigger result when adding a new customer

record?

Below is the trigger script:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-  
- - - - - - - - - -

CREATE TRIGGER dbo.trTrackInsert

ON dbo.Customers

FOR INSERT

AS

BEGIN

-- SET NOCOUNT ON added to prevent extra result sets from

-- interfering with SELECT statements.

SET NOCOUNT ON;

-- Validate the new record.

-- Criteria:

-- 1. Check if there is already a record in the NewCustTracker

-- 1.1. If no record add to the table and record the user info

-- 1.2. If there is record

-- 1.2.1 Inform user that there is pending new record to be completed

-- 1.2.2 Perform roll back of the insert in the Customers table

-- Initialize variables to use in getting some info in the NewCustTracker 
and Customer

-- tables.

DECLARE @[EMAIL PROTECTED]
 int;

DECLARE @[EMAIL PROTECTED]
 nvarchar(200);

SET @[EMAIL PROTECTED]
 = 0;

SET @[EMAIL PROTECTED]
 = '';

-- get the record count in the dbo.NewCustTracker table

SET @[EMAIL PROTECTED]
 = (SELECT count(*) FROM dbo.NewCustTracker);

BEGIN TRANSACTION insertIntoNewCustTracker

IF (@[EMAIL PROTECTED]
 > 0)

BEGIN

-- get the info in the NewCustTracker table...

SET @[EMAIL PROTECTED]
 = (SELECT UserName FROM dbo.NewCustTracker);

RAISERROR(N'There is a pending new customer record to be completed by %s. 
Please recheck in a couple of minutes.',16,1,@[EMAIL PROTECTED]
);

ROLLBACK TRANSACTION insertIntoNewCustTracker;

END

ELSE

BEGIN

-- record the new customer record in the NewCustTracker table for next 
validation...

INSERT INTO dbo.NewCustTracker(CustNum, UserName)

SELECT [Customer Number], user_name() FROM inserted;

IF @[EMAIL PROTECTED]
 > 0

COMMIT TRANSACTION insertIntoNewCustTracker;

END

END

GO

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-  
- - - - - - - - - -

Any ideas/suggestions are appreciated.





Thanks,

Ben
 




 9 Posts in Topic:
Handle Triggers in MS Access 2003 with SQL Server as Back-End
"Ben" <pilla  2008-04-12 22:37:48 
Re: Handle Triggers in MS Access 2003 with SQL Server as Back-En
"Linq Adams via Acce  2008-04-12 23:14:41 
Re: Handle Triggers in MS Access 2003 with SQL Server as Back-En
"Ben" <pilla  2008-04-12 23:20:01 
Re: Handle Triggers in MS Access 2003 with SQL Server as Back-En
"Rick Brandt" &  2008-04-13 00:24:33 
Re: Handle Triggers in MS Access 2003 with SQL Server as Back-En
Tom van Stiphout <no.s  2008-04-12 17:43:59 
Re: Handle Triggers in MS Access 2003 with SQL Server as Back-En
Erland Sommarskog <esq  2008-04-13 01:57:12 
Re: Handle Triggers in MS Access 2003 with SQL Server as Back-En
Ed Murphy <emurphy42@[  2008-04-14 19:15:36 
Re: Handle Triggers in MS Access 2003 with SQL Server as Back-En
"Ben" <pilla  2008-04-19 07:09:06 
Re: Handle Triggers in MS Access 2003 with SQL Server as Back-En
"Ben" <pilla  2008-04-19 08:00:42 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Wed Dec 3 1:24:55 CST 2008.