E
Eric
I'm getting '#error' showing on previewed and printed
reports but only on 1 or 2 PC's. The problematic fields
have calculations in the underlying query. Upgrading the
PC's solves the problem, but is their a cheaper solution?
reports but only on 1 or 2 PC's. The problematic fields
have calculations in the underlying query. Upgrading the
PC's solves the problem, but is their a cheaper solution?