on 04-15-2013 5:59 PM
Hi Folks,
Have kind of a hot one here.
I throw this out in case it's quick fix that a lot of people have already seen.
The same file stored in a report directory or library can be opened without a hitch with Excel 2003 and Excel 2010 on a Windows XP machine.
That same file will crash excel when it is on an a Windows 7 machine.
Thanks in advance,
-Greg
p.s. I will also open a ticket with SAP per our SLA agreement
Turns out this is the answer, from another thread:
http://scn.sap.com/message/10546044#10546044
Former Member Mar 1, 2012 11:59 AM (in response to Geoff Barker)
Hi Velázquez
Thanks for your inputs.
Working together with Sap, we eventually found that the problem was due to having some obsolete second or third EVDRE functions in the problem reports (which were not deleted) which contained junk characters and when running BPC client 7.0.118 on Windows 7 only, the crash occured.
Sap acknowledge it was a bug with these specific combinations (Windows 7 / client 7.0.118) as there was no issue when running under XP or Windows 7 running 7.0.113 front end.
Regards
Geoff
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just a thought, but we've seen some odd things with our Excel 2K3 files on XP/Win7 Machines... in some cases, it was simply the filetype/extension. See if you have the file saved as a 2K3/2K7 Excel version.
In some of our issues, just changing the file extension for templates back to .xlt instead of .xltm worked for us, but we've had a few other "buggy" issues we are still working through.
Good luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.