Closing a form causes Non related error dialog

[toddbailey]

Hi All,

After several years in production with out this error, the users are now getting an error dialog when they close a form.

There are 2 forms that interact, a switchboard that has a couple of command buttons (docmd.openform for example)

when the user clicks the button the switch board is closed and the new form is opened. when the form is then closed also via a button (docmd.close) the switchboard is opened but we see a dialog box
"the changes you requested to the table were not successful......"

This would indicate that an update or an insert is being performed that violates a key constraint.

But, there isn't any database updates/inserts being performed switching between the 2 forms. At least not that I can detect, there isn't an vb/a code being executed that do any database related processing.

I've tried using docmd.setwarnings false to disable the display of the dialog to no avail and also tryed a database compact/repair with out any success

Any ideas how to troubleshoot this or at least disable the warning dialog?

 

[spikepl]

1.Access never lies. On almost all occasions an error message is specifically related to the issue described in the message.

2. To disable error messages just because you do not understand what caused them is a really bad patch.

3. Access tells you that changes were requested. So changes were requested, no matter what your opinion is.

4. Closing a form causes a an update of the record the thing is on, if the record is dirty.

5. Just because something ran without fault for a long time is no guarantee of anything. A user could have inserted some data in the db that was not completely verified by accident or unhandled error, or even via a handled error that did not foresee the particular situation.

6. Take a copy of the db and play with the copy. Inspect the data -some might be not what you expect. Also, identify which data causes the error to occur - you can start erasing data from the copy and see whether the problem still arises. Also, in the form that causes the issue, what data is in that form? What triggers the dirtying of the form (and, in turn, the save that fails)? WHich data does it not like?

 

[toddbailey]

OK, thanks.


I just needed to make sure that this wasn't some funky bug that MS never bother to fix.

I agree taht suppressing error messages is not the best solution but there are times when you have no choice...

anyway, I continue my efforts on isolating what's causing this...