Reserved Error #16389, Access 2003 SP3

[niobium]

Hello all,

After a search of Google and Google Groups, I have not found any
indication of a solution or known specific cause for the Reserved
Error. I did find 2 threads about it on a pair of forums, but in one
case no one ever replied with a solution or cause, and in the other,
the developer gave up and just began trapping the error.

The odd thing for me is, despite having made no changes to any of my
subroutines throwing this error, it's now cropping up in, near as I
can tell, any case where a form is in DataEntry mode, and either
switches to DataEntry = False, or, Saves via DoCmd.RunCommand
acCmdSaveRecord, in VBA code.

In the case mentioned above where the dev trapped the error, his code
was saving, and then requerying on a combo box to update it. So, not
exactly the same, but he is saving as well and was getting the same
"Reserved Error" and number (16389). An additional piece of
information this dev related was that he said the same code did not
produce this error in Access 2000.

If I trap the error the record saves out just fine, and nothing is
wrong with the underlying data in the tables, but does anyone know
WHAT specifically causes this one? I've been searching all over and I
can't seem to find much useful information (aside from 'trap it').

This is an Access 2003 SP3 client, with SQL Server Express

--Niobium

 

[Clif McIrvin]

I have no idea if this is related or not, but do you have the SP3
hotfix?

 

[Niobium]

Cliff,

I did actually apply that one--previously we all had to stay at SP2
because one of the bugs was a serious problem for us. So we stayed at
SP2 and then patched to SP3 and used the hotfix, and everything was
fine on that front. (I suppose I can roll back one of the test
machines and see if it shows up in SP2.)

It's odd because this only came up in the last, I'd say month or so,
and it's showing up in code we haven't changed, so it seems more like
some recent Office update is doing it. But I can't find any mention of
what that might be, or if it's a configuration setting, or what; just
the work-around to trap the error and go on with life.

--Niobium

 

[Niobium]

Success! I managed to narrow down the occurrences on one specific
form, and I finally identified the source--my Resynch Command.

I didn't realize is was the Resynch earlier because it was for a form
whose source View was one where only updating the Unique table was
sufficient (otherwise I might have seen some missing/incorrect
information on related tables).

Whew!

--Niobium

Cliff,

I did actually apply that one--previously we all had to stay at SP2
because one of the bugs was a serious problem for us. So we stayed at
SP2 and then patched to SP3 and used the hotfix, and everything was
fine on that front. (I suppose I can roll back one of the test
machines and see if it shows up in SP2.)

It's odd because this only came up in the last, I'd say month or so,
and it's showing up in code we haven't changed, so it seems more like
some recent Office update is doing it. But I can't find any mention of
what that might be, or if it's a configuration setting, or what; just
the work-around to trap the error and go on with life.

--Niobium

I have no idea if this is related or not, but do you have the SP3
hotfix?