Write conflict error after adding trigger to table

Hi everyone,

I have inherited an Access adp that directly connects to SQL Server. My
knowledge is mostly at the SQL Server level and I have worked with older
versions of MDBs - Access 97 and previous. I created delete, insert, and
update triggers on the table an Access form pulls up through a stored
procedure that selects the recordset. When you change to a new record, it
runs the save (I added a check for Me.Dirty, but it still considers it dirty
even if the user didn't make any changes. There is a lookup feature on this
form. Every time I try to change records using the lookup feature (it does
"If Me.Dirty = True Then DoCmd.RunCommand acCmdSaveRecord"). It says the
record has been changed by another user since you stared editing it. etc,
etc. The trigger inserts a row into another database through a view in
that database. The user has access to the view and full rights to the table
with the trigger in it. What is the deal? If I use that user ID through a
linked table in Access, they can change the record. However, if I run the
stored proc in the database window instead of through the form, it still has
the same error, so it is not the fault of the form, but of using the stored
proc as a datasource. Can anyone clue me in? Is this an Access bug, and if
so, how do I get around it? This is very frustrating because the Access app
is preventing me from rolling these triggers to production where other apps
(.NET) that hit the triggers have no problems (but of course, they don't use
that stored proc).

Thanks,
MH


.

Relevant Pages

  • Re: Help with SQL 2005 and Sourcesafe 6
    ... that update the stored proc in the database, or do you just simply update it ... We already use Microsoft VIsual SOurcesafe 6 to store our ... Obviously the stored procedures have to be in the database for SQL Server ...
    (microsoft.public.sqlserver.tools)
  • Re: Audit trail for web application
    ... This is more of a SQL Server question than an ASP.NET question. ... with implenting auditing at the application level or using table triggers is ... There are also 3rd party database auditing tools that should do ... > I am trying one approach with the help of triggers. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: SQL Server Express versus Access (In the World Series of Love)
    ... If your need involve a form, then triggers are not an appropriate tool: ... after a change in the database. ... OF triggers to achieve the same, say, over view, so, advantage to Jet. ... MS SQL Server may have a horse shoe maker right out of the box, ...
    (microsoft.public.access.modulesdaovba)
  • Re: How to tell if a stored proc included a Select statement
    ... Vyas, MVP (SQL Server) ... Is .NET important for a database professional? ... stored proc whether another stored proc that it has called populated a ... can the calling sproc know if the called sproc populated a result set? ...
    (microsoft.public.sqlserver.programming)
  • Re: ANSI_WARNINGS inconsistently in effect
    ... Vyas, MVP (SQL Server) ... The problem is that one client is getting an error with the update failing ... I realize that I could put the update in a stored proc and set ANSI_WARNINGS ... The ANSI_WARNINGS db_option for the database is FALSE. ...
    (microsoft.public.sqlserver.clients)