I'm sure there's a very simple solution, but it seems to be eluding me -- I have a db application (MS Access Front End/Azure SQL Back End) -- I have triggers written on certain tables (for example, if an error occurs, a record is added to an error log table) that send an email to me after a record is added to that table. When the records are being added by me, or by a job, everything works fine.
When an end user tried to add a record (using the same example, an error occurs, my code attempts to add a record to an error log table), it fails, and it fails entirely because of the trigger. When I remove the trigger, or even just the actual mail sending portion of the trigger, the record is added to the table.
Login to SQL Server is through windows authentication, however all the end users are lumped in together in windows group, so the user list for the db is something like this:
sa, OURCOMPANY\jsmith, OURCOMPANY\fjones, OURCOMPANY\endusergroup
I suppose I could have a job running every 5 minutes that checks if records are being added to certain tables, and then execute sending an email through that job, but there must be some simple setting I'm missing.
Thanks for taking the time to read this -- any thoughts would be greatly appreciated.