hi,

i'am struggling for some time with a form in ac2003. Sometimes occurs an
error with number 3167. In that form i fill some textfields automaticly with
a commandbuttum. In that command , i only navigate in the form to a former
record , get the last value of a certain field, then i navigate to the
currend record and fill it with value + 1. No big deal. It works fine for
some time, but nowdays i get the error that the record is deleted. It occurs
not allways. i can occur after 10 or twinty times , but it also can occur
after one record i fillied in. Last i did some tests when it does occur
for, at least 100 times with ... no error. Therefore i cannot set a
breakpoint because i'am not certain the error occurs. I've read a lot about
it and put all my data in a new db but without succes. There are no
memofields or ole-objects in my form. The form is based on data from 4
tables
When the error occur, i have to manualy delete the record(###, in all fiels)
in the table and do a compact and repair afterwards. It's strange that when
i "compact and repair" the primary key is vanished. i have to set it
manaually again. You see , this is not a kindly methode to resolve this
problem.
Is there someting i can do yet or can if prevent this in my errorhandling ?

regards, Bob

I suggest you post the VBA code you are using to do this. Someone may be able
to look at the code and suggest an alternative to what you are doing.

It might help if you also include the form's record source (the query the form
is based on).

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

Bob wrote:

Bob wrote:
sounds like you are entering a new record, then move to another record,
then move back to the new record which I assume is now saved.

Or are you finding a record in a recordset and getting the value and
updating the current record with the value+1.

Do you have an error routine running? What happens if you remove the
error trapping temporarily so you can find the line it breaks on. Then
check the values contained on that line? Do you call any external
functions or subs in the routine it breaks on? For example, if it
breaks when you press a command button, that button may call a routine
that calls another routine that calls another routine. It might be
something way down the list that is goofing up.