I have a sql server 2005 table called foo
it is an access2007 linked table
with a form using bound fields (qmsResponsibility, ncoType)
part of an afterUpdate event does this


7
If (Nz(qmsResponsibility, 0) = 20) Then
ncoType = 1
Else
ncoType = 2
End If
8
fExit:
On Error Resume Next
Exit Sub

fErr:
msgbox err.description & " " & Erl
Resume fExit

I get a msgbox with
Record in table 'foo' was deleted by another user

and erl is 7

in order to get to the afterUpdate event, the user has selected
one specific record from table foo

other than the obvious, ie. another user did in fact delete this
record? what else can cause this error ?

I may be on the wrong track - but see if adding a "timestamp" type field to
the table fixes the problem.

"Roger" <lesperancer (AT) natpro (DOT) com> wrote

Roger wrote:
In google I found the following.
http://msdn.microsoft.com/en-us/libr...ice.12%29.aspx

There's this as well
http://www.granite.ab.ca/access/corruption/symptoms.htm
and
http://www.corrupteddatarecovery.com...ther-user..asp

On Feb 23, 7:07*am, "aceware" <acew... (AT) iinet (DOT) net.au> wrote:
thanks, but I already have a timestamp field

On Feb 23, 7:58*am, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
my form is set to 'no locks' (optimistic) locking
changing it to pessimistic locking (edited record), locks pages which
could prevent someone from updating another record in the same page -
is this a problem with access2007 ?

as to the other two links, the sql server data is not corrupted

I have found that Access sometimes reports errors that seem unrelated to the
actual problem.
On the assumption that the code in the afterUpdate event references
controls/fields on the same form, I think you are setting up an endless
circle.

The record in the form is updated, which triggers the afterUpdate event,
which then dirties the form again, which then must be saved again,
triggering another afterUpdate event.

If you want ot modify the same record after saving it, try using the
recordsetclone. That won't dirty the form.

Also make sure that Access recognizes the primary key in the table that the
form is bound to.
--

AG
Email: npATadhdataDOTcom


"Roger" <lesperancer (AT) natpro (DOT) com> wrote