Crystal report Error when trying to export data only .xls within

Yahoo Archive
1
We are at 9.04.506C and had that problem.
We installed the latest version of crystal runtime on users pc and the server,
Crystal Reports XI R2 SP6 Runtime
and that helped.
We still have a few users with issues that can't run it on their PC's - which I'm wondering if it is a rights issue - I haven't been able to figure that one out, but this has worked for some of our pc's and users.





--- In vantage@yahoogroups.com, "pklein256" <pklein@...> wrote:
>
> When I do a print preview and try to export the crystal report to a spreadsheet as data only.xls I get the following error.
>
> ---------------------------
> Crystal Report Windows Forms Viewer
> ---------------------------
> Error in File C:\DOCUME~1\pklein\LOCALS~1\Temp\tmpD72 {C52B8F0C-4357-4519-8963-8A17E8437960}.rpt:
> Operation not yet implemented.
> ---------------------------
> OK
> ---------------------------
>
> this happens on new BAQ reports (old ones carried over from Vantage work ok)
> Any ideas?
>
2
When I do a print preview and try to export the crystal report to a spreadsheet as data only.xls I get the following error.

---------------------------
Crystal Report Windows Forms Viewer
---------------------------
Error in File C:\DOCUME~1\pklein\LOCALS~1\Temp\tmpD72 {C52B8F0C-4357-4519-8963-8A17E8437960}.rpt:
Operation not yet implemented.
---------------------------
OK
---------------------------

this happens on new BAQ reports (old ones carried over from Vantage work ok)
Any ideas?
3
This is a known issue. The only work around we have found is to load Windows 7 on the machines that absolutely need it.

Crystal plans on releasing a fix, but there isn't an ETA. Maybe we will get lucky and it will be included with the Crystal updates in .601 :-)

--- In vantage@yahoogroups.com, "pklein256" <pklein@...> wrote:
>
> When I do a print preview and try to export the crystal report to a spreadsheet as data only.xls I get the following error.
>
> ---------------------------
> Crystal Report Windows Forms Viewer
> ---------------------------
> Error in File C:\DOCUME~1\pklein\LOCALS~1\Temp\tmpD72 {C52B8F0C-4357-4519-8963-8A17E8437960}.rpt:
> Operation not yet implemented.
> ---------------------------
> OK
> ---------------------------
>
> this happens on new BAQ reports (old ones carried over from Vantage work ok)
> Any ideas?
>
4
We have the issue as well (9.04.506C). On 4/19/2011 I got an email from David Guerra at Epicor Support saying it was fixed (on SCR 6153ESC) but it isn't... we still have the problem and I told him so. No further word. The call has been closed.

Ernie Lowell
Diba Industries

--- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@...> wrote:
>
> >> Crystal report export Data Only error
> >> Operation not yet implemented.
>
> >>> This is a known issue.
> >>> Crystal plans on releasing a fix,
> >>> Maybe we will get lucky and it will
> >>> be included with the Crystal updates in .601 :-)
>
> Has anybody ever received any more details on this?
> I'm having a problem with a BAQ report.
>
> When I called Epicor, the tech didn't know anything about it.
> I was sent a Crystal Guide & tried all the suggestions.
> Data Only export still failed, as soon as I added more than one field to the report.
>
> --- In vantage@yahoogroups.com, "Jen" <jmesiano@> wrote:
> >
> > This is a known issue. The only work around we have found is to load Windows 7 on the machines that absolutely need it.
> >
> > Crystal plans on releasing a fix, but there isn't an ETA. Maybe we will get lucky and it will be included with the Crystal updates in .601 :-)
> >
> > --- In vantage@yahoogroups.com, "pklein256" <pklein@> wrote:
> > >
> > > When I do a print preview and try to export the crystal report to a spreadsheet as data only.xls I get the following error.
> > >
> > > ---------------------------
> > > Crystal Report Windows Forms Viewer
> > > ---------------------------
> > > Error in File C:\DOCUME~1\pklein\LOCALS~1\Temp\tmpD72 {C52B8F0C-4357-4519-8963-8A17E8437960}.rpt:
> > > Operation not yet implemented.
> > > ---------------------------
> > > OK
> > > ---------------------------
> > >
> > > this happens on new BAQ reports (old ones carried over from Vantage work ok)
> > > Any ideas?
> > >
> >
>