When trying to run MR-G (Print Materials Requirement) using the Planner Code field as the filter, we are receiving error messages saying "Too Many Pops". It will finish the report & only a small amount of the data will actually print out. This started occurring after the most recent upgrade we installed in the last 30 days.  
 
Any reason why this may be occurring & how do you fix it?
 
Thanks!

The Too Many Pops message would be program specific - exactly what point in the program do you see the message?  Do you sat T or No to the question about a new page fpr each part number?  Any other folters besides Planner Code?  I just tried here and can't duplicate so I need to know exactly how you are running the report.

Lynn,
 
All we chose to change was the Planner code. We also tried to only use Category as well as Class & we still got the message.
 
Sharon

Allen
 
Well, we had a very odd thing happen yesterday that is probably related.  We had a part correctly appear on a work order traveler but it did not show up on the picklist.  When I went to look at the part in IN-A nothing came up.  This is an old part (type R) with hundreds of transactions.  When I ran an inventory transaction report all of the info was there.  I then used Crystal to look at the MTICMSTR and BKICMSTR and sure enough it wasn't in the BKICMSTR.  But, it was in the MTICMSTR as well as INTXN, WOBOM, etc.  I then added it back into the system through IN-B (probably the wrong thing to do) and all of the history linked up to it.
 
When I used Maintain Database to look at the part again I noticed we now have 2 lines for this part in MTICMSTR and only one in BKICMSTR.  Also, both files have the same number of records.
 
I am not sure how to check to see if I have this problem with any other parts.  Do you know how we got into this mess?  And, as of this morning, we are back to classic DBA (ugh!!!!).  We have had a lot of instability and have had to reboot our server daily (sometime more than once!).  I am suspecting the instability has to do with adding more users in recent months.  And, I suspect that one of the times DBA crashed is when we corrupted the file for that part.
 
Thanks for any help you can provide.
 
Sharon (Dave too)