Report runs in preview mode, crashes or fails in print mode

SOLVED

This is one of those crystal oddities. I have a custom report that works fine in preview mode. When printer destination is set to printer, the admin user can run it ok, but all the other users can't run it. The report fails before it prompts for the first variable which is a date. The preview date prompt is also ever so slightly different (like a different version of Crystal) from the Printer dest date prompt. We have the customization directories set for all users to be the same directory which is on an application server. (So, we are not talking about an installation where the program files are on the workstation, the whole shebang is on the server). Actually, all the custom reports work this way - print preview is fine, but print dest = printer only works for the Sage admin user. 

Any thoughts? 

Sage 300 2020, perpetual license, SQL database. 

Parents
  • 0

    The other thing I had to do for a user was to add a bunch of Sage user authorization privileges. So, the question is how can I efficiently determine which authorizations privileges I will need to run a crystal report. The problem is that the set of privileges that worked for Sage 2012 does not work with the same report for Sage 2020 which doesn't make any sense to me. If the authorization privileges are insufficient, the behavior is that Sage might crash or else the program does not complete. 

  • 0 in reply to Peter.Heinicke

    If you have to mess with privileges, then your reports aren't written correctly.  Never use NT authentication, always use login and password inside the Crystal editor.

Reply Children