Emerald does NOT use OBBC (it talks directly to SQL Server). However,
the print engine DOES use ODBC. Therefore, its very common for an
ODBC configuration issue to prevent printing, with Emerald working just
fine. The Error you are getting means that the print enginer couldn't
find/connect to the SQL Server defined in the ODBC DSN.
> > 1. I cannot get any reports or invoices to print. I have not been able to
> > since I installed the software 2 months ago. So, this is a first time
> > problem, that has not been caused by an upgrade or anything. I get the
> > error: StartprintJob in PrintCustom caused an error: Cannot open SQL.
> > I tried opening the SQL Executive and gave the user Full rights to
> > everything in the database. I have them with full rights in the Emerald
> > Administrator. What am I doing wrong? Can you give me a step by step
> > instructions on how to resolve this issue?
> Most likely this is an issue with your Emerald ODBC DSN. Make sure
> its pointing at your SQL Server and that the username/password you
> are using to login to Emerald works with that DSN. Typically this
> is an issue like use trusted connection is checked in the DSN, and
> you don't have a trusted connection to your SQL Server (ie, it
> should be normal, not trusted).
Dale E. Reed Jr. Emerald and RadiusNT/X__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart