Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Report Restriction Problem

Status
Not open for further replies.

Borvik

Programmer
Jan 2, 2002
1,392
US
I have several restrictions on SOP Blank Order Form, one of which I think is causing a problem with printing.

The one in question is laid out like so:

(SOP_Serial_Lot_Hist.SOPNUMBE = SOP_Serial_Lot_Hist.SOPNUMBE) AND (SOP_Serial_Lot_Hist.SOPTYPE = SOP_Serial_Lot_Hist.SOPTYPE)

To me this doesn't look like it is doing very much (does it equal itself ok print).
I've removed this at one point and when printing I get the following complaint:

"Inconsisten restriction/sort expression. Please add the following restriction D03301SOP Type = D03301SOP Type."

Now I don't think there is any reference in the sort to this field as I've checked the Sort window from Report Definitions, and nothing was in the Sort By listbox.

There are two other restrictions however, but I don't see them as the cause of that either - for completeness sake here they are:

SOP_HDR_WORK.Batch Number <> "DROPSHIPPED"

EXISTS(SOP_LINE_WORK.QTY to Invoice > 0 AND SOP_LINE_WORK.Drop Ship = 0)

Apparently when the report is printed off, several orders do not print that should have (i.e. Batch Number is not DROPSHIPPED, they have QTY to Invoice and are not Drop Ship does equal 0). The only thing I can think of is the other restriction, but I get that complaint from the system when I remove it.

Any ideas?
 
Sometimes the report writer gets confused when it creates the relationships and restrictions. Adding the restrictions which link a field to itself seem to help fix the issue.

Please don't ask me why!!!!

David Musgrave [MSFT]
Senior Development Consultant
Escalation Engineer
MBS Support - Asia Pacific

Microsoft Business Solutions

mailto:dmusgrav@online.microsoft.com

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.
 
Yes that does seem to be the case. But it seems to me that that restriction is also causing problems for our automated printing (ex. Documents not printing that should).

Guess I'm just trying to find a way around it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top