Glad to hear it and thanks again.
 
Unfortunately, I have another problem. This one has racked the brains of an accountant and myself for the last hour. We should have come to you first!  
And sadly this was a problem that has been in the system since 2002. Apparently people before me didn't do much of a good job of keeping the system clean and up to date.
 
We have a PO that was received into QC by accident. Following transactions. The receiving department went into "Receive Purchase Orders" (PO-C) and tried to back out the 3 that was received into QC. However, they received the negative from inventory and not QC. Which of coarse left a -3 in RNI. So, they turned around and received 3 more into inventory to fix the negative qty and get RNI back to 0.
Which "in theory"   should leave the 3 in QC. When you run the report "Print Open Purchase Orders Listing" (PO-I-A) it shows 3 in QC.
However, when you go to QC to buy off the 3 or minus it out. It says "Qty Remaining" is 0. And is showing the "Bought off to date" as 3.
Now the question is. How is it that Qty remaining is 0 and yet the open purchase order listing shows 3 in QC. We've even tried to just purge the system by closing or deleting the PO, but of coarse we can't do either because there are "items that have been received but not invoiced". And from the PO reports the only thing showing open, RNI, QC, or anything on this PO are the "3 in QC".
We've tried doing a -3 from QC in "accept/reject/use as is" and each entry adds -3 to RNI and 3 more to the qty in QC (totaling 6)? We even tried receiving a positive 3, once we got the RNI to 0 and QC qty back to 3, and it won't let you because is says we are trying to receive over the remaining qty. (which again it says is 0)
After all this and the PO being so old we'd be happy even deleting the PO from the system but it won't let us do it.  
Do you know how to delete or close in this situation or if you know the solution to getting the items out of QC that'd be great as well.
 
Thanks again for your help.
Jon
 

The only solution that I know of is to fix this field by field for the affected tables in Maintain DB....