^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ Darin Spence
darin@radio-inc.com
Director of Information Technology > R A D I O, INC
(785) 628-1064, ext. 22 > Phone
http://www.media-net.net
> -----Original Message-----
> From: emerald-request@iea-software.com
> [mailto:emerald-request@iea-software.com]On Behalf Of Josh Hillman
> Sent: Thursday, June 03, 1999 5:44 AM
> To: emerald@iea-software.com
> Subject: Re: [Emerald] Printing error.
>
>
> From: Todd Hutchinson <emerald@FISolutions.com>
> > Yes CR 6.0 PRO works, however the CR 6.0 doesn't.
>
> Have you tried reinstalling Emerald 2.5 afterward (installs the necessary
> print-related files)? Maybe the installation of your CR did something to
> one of the print-related files used with CR/Emerald.
>
> Josh Hillman
> hillman@talstar.com
>
> >-----Original Message-----
> >From: Josh Hillman [SMTP:admin-maillist@talstar.com]
> >Sent: Wednesday, June 02, 1999 3:40 PM
> >To: emerald@iea-software.com
> >Subject: Re: [Emerald] Printing error.
> >
> >From: Darin Spence <darin@radio-inc.com>
> >>I'll definitely post, if we find a solution. I have called Crystal
> Reports
> >>and they have pretty much wiped their hands of it, what they
> explained to
> >me
> >>makes sense. Either way, several had mentioned at IEA that a
> request had
> >>gone to Dale to get a 'Print Debug' version of Emerald.exe to me so that
> we
> >>can figure out where the disconnect. Alas, many weeks have
> passed and no
> >>answer yet. However, they are very busy. I know they won't forget...
> >
> >I'm using CR 6.0 Pro on my NT 4.0 SP5 workstation and have Emerald 2.5
> (half
> >a dozen different versions) and all of them can print without any kind of
> >problems. Maybe your Emerald DSN isn't configured correctly in the ODBC
> >config area of the Control Panel??
> >
> >Josh Hillman
> >hillman@talstar.com
> >
> >>> -----Original Message-----
> >>> From: emerald-request@iea-software.com
> >>> [mailto:emerald-request@iea-software.com]On Behalf Of Todd Hutchinson
> >>> Sent: Wednesday, June 02, 1999 1:17 PM
> >>> To: 'emerald@iea-software.com'
> >>> Subject: RE: [Emerald] Printing error.
> >>>
> >>>
> >>> If you find the answer for this please post to this group,
> >>> we have known
> >>> about this since dec 1998 and have never been able to get by that
> >>> problem.
> >>> Everything worked fine until we installed CR 6.0 on one of the
> >>> workstations, after that it would never print from Emerald again. Our
> >>> solution was to print for a workstation that didn't have CR 6.0 on it.
> I
> >>> worked with IEA on this and they stopped looking into it
> after we linked
> >>> the install of CR 6.0 to the printing problem.
> >>>
> >>> -Todd Hutchinson
> >>> FISolutions Inc.
> >>>
> >>> -----Original Message-----
> >>> From: Darin Spence [SMTP:darin@radio-inc.com]
> >>> Sent: Tuesday, June 01, 1999 12:08 AM
> >>> To: emerald@iea-software.com
> >>> Subject: [Emerald] Printing error.
> >>>
> >>> Oops, the cast number was actully 822335.
> >>>
> >>> ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ Darin Spence
> >>> darin@radio-inc.com
> >>> Director of Information Technology > R A D I O, INC
> >>> (785) 628-1064, ext. 22 > Phone
> >>> http://www.media-net.net
> >>>
> >>> > -----Original Message-----
> >>> > From: emerald-request@iea-software.com
> >>> > [mailto:emerald-request@iea-software.com]On Behalf Of Darin Spence
> >>> > Sent: Tuesday, June 01, 1999 12:05 AM
> >>> > To: emerald@iea-software.com
> >>> > Subject: RE: [Emerald] Mass Updating Payments
> >>> >
> >>> >
> >>> > I called the VB Script people at Seagate Crystal Reports to ask if
> they
> >>> > could offer any insight as to why I am getting the DSN=Emerald error
> >>> > whenever I try to print from Emerald.
> >>> >
> >>> > They had me go through a few things and finally noted that
> it appears
> >>> > Emerald is trapping the error and they are not sure if it
> is trapping
> >an
> >>> > internal error or a crystal reports error. If it is a Crystal
> >>> > Report error
> >>> > that is being trapped, they need the error code and will work to get
> it
> >>> > figured out for us. If it is an Emerald error that is
> being trapped,
> >>> then
> >>> > there isn't anything they can do.
> >>> >
> >>> > I am anxious to print from my workstation. Has Dale made any
> >>> > progress on a
> >>> > debug version that we could use to get this figured out? I worked
> with
> >>> > Shawn again last week and he noted that this needed to be esclated.
> >>> >
> >>> > If it is determined that Emerald is trapping a Crystal Reports
> >>> error, the
> >>> > seagate group can be reached at (604) 669-8379, the tech to talk
> >>> > to is Chris
> >>> > at extension 427 and the case number was 427.
> >>> >
> >>> > Please let me know if there is anything I can be doing on
> this end to
> >>> move
> >>> > this process along.
> >>> >
> >>> > Thanks!
> >>> >
> >>> > ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ Darin Spence
> >>> > darin@radio-inc.com
> >>> > Director of Information Technology > R A D I O, INC
> >>> > (785) 628-1064, ext. 22 > Phone
> >>> > http://www.media-net.net
> >>> >
> >>> >
> >>>
> >>>
> >>
> >
> >
>
>