OE forms - Database login

Printing customized forms - Database login screen. I have no issue printing order confirmation, invoice or credit note in V6.0a. But when printing in Sage 300 V2016, I am getting the database login windows - any ideas what needs changing to the forms to prevent the login screen from popping up?

They are not datapipe reports.

Many thanks

Caroline

  • 0
    Did you edit OERPT.INI and comment out the datapipe lines?
  • 0 in reply to Jay Converse Acumen
    I thought this is no longer necessary in V2016. This oerpt.ini - comment out datapipe lines normally affects the invoice. My invoice is printing fine. It's only the order confirmation and credit note. Similarly for PO, PO is printing fine without any database login window but not for the receipt.
  • 0 in reply to Cnagle
    Assuming these are customized forms,make sure there are no non-Sage tables, and the properties of the datasource connections in Crystal are not "Trusted Connection: 1"
  • 0 in reply to Jay Converse Acumen
    Many thanks Jay, this is really strange, all my forms have got SQL views - order confirmation, invoice, credit note, po and po receiving list. They also have trusted connection set to 1 for all of them. But the only 2 that are printing without the login window popping up are the invoice and PO. All the others are popping up with login window. If I deselect the Use Integrated Security check box and click Finish. It will print, but this is a real pain with 2 extra clicks. I am really puzzled. Still trying to find the difference in the ones that work and the ones that do.
  • 0 in reply to Cnagle
    Version 6.1 introduced a new crystal runtime. Like mentioned prior, custom forms/reports that referenced anything not in the data dictionary now require the report to be configured for integrated security or you get the db login screen. This has security advantages but is also a pain because you have to create sql user accounts. A work around is to reference whatever is not in the data dictionary using a sql command. The new crystal runtime does not have the same db login issue with sql commands.
  • 0 in reply to angel g
    Hi Angel, thank you for your information. Can you share an example of how to configure the report for integrated security? What do I need to do to the SQL view in order to achieve this - s to reference whatever is not in the data dictionary using a sql command. Thank you very much in advance.
  • 0 in reply to Cnagle
    You don't have to change anything in the view. You just need to change the datasource in the actual report. In crystal designer go to Database>Set Datasource Location. In the current datasource section select the view. In the the replace with section expand the connection that has the view, right click on Add command and select Add command to report. Your command would be something like "select * from viewname". If you are using commands in your datasource you can uncheck use integrated security.
  • 0 in reply to angel g
    Many thanks again. The ODBC data sources are set without using integrated security. I did what you say about the Add Command, but when I do that nothing happens. Will it be possible to have a chat with you? My email is [email protected]. Thank you again.