R
raymondhall
A complicated single page Crystal Reports form which works perfectly
from an operational access 2000 .mdb appears to have a capacity
problem when run from a SQLServer7 recordset. The full form gives a
Crystal error message referring to paging problems. The form with
only half the fields on prints but shows garbage in many fields. The
form with only a minimum of fields works OK.
Could someone tell me where the problem is and hopefully suggest a
solution?
from an operational access 2000 .mdb appears to have a capacity
problem when run from a SQLServer7 recordset. The full form gives a
Crystal error message referring to paging problems. The form with
only half the fields on prints but shows garbage in many fields. The
form with only a minimum of fields works OK.
Could someone tell me where the problem is and hopefully suggest a
solution?