> For some reason, one of the computers that we are running Emerald on will
> no longer print. We get a "ODBC=Emerald" and then "You have no Emerad DSN
> configured.....". All we have done on that computer is re-installed MS
> Office. We have both a user and system DSN configured, and have tried one
> or the other by itself, and it does the same thing. We have reconnfigured,
> reinstalled, and rebooted, still no luck. Have you seen this happen before?
The 2.1.11 client verifies the ODBC DSN before printing. Unfortunately,
it does it in a case sensitive manner. Make sure the DSN is EXACTLY
"Emerald" and it will work.