Thank you for the response Barry.

Yeah, I could do that to just logically to determine I cannot write to the document but I was looking for the specific error to test for that would occur if fixup was running.  Testing the way you mention would just say I can not touch this document so I could move on to the next document, and the next, etc.  Each would fail.  But if I knew which error was passed back because of fixup running then the code would be able to just close the DB being there is no way we could process any document in the DB until after the fixup is complete.  If someone knows then great but if not I can run some tests later tonight to determine.  I am just concerned that fixup will be finished so fast in my testing that I will not be able to run my code fast enough to determine the error.....  Actually I think I have a plan, I could write some code to just open database, open document, get field test, if 1 change to 2, if 2 change to 1, NSFNoteUpdate, if error print error on screen.  While loop is running then run fixup against the database.  I think a test like this could work.