Hey Folks…
I have a user that runs a query, clicks on data, then view, then export. He’s trying to export the data to an Excel format. When he does so, he receives a “Syntax Error in Field Definiton (3292)” any clues. Thanks…
Normal is the average of extremes
Michael Dempsey
Manager, Data Base Administration
University of North Carolina Hospitals
eMail MDEMPSE.ISD1@MAIL.UNCH.UNC.EDU
Listserv Archives (BOB member since 2002-06-25)
This is caused by an ‘unusual’ character on one of the objects. It might be the ‘&’ character. Check the variables for these kinds of characters. I had one report that just wouldn’t export to Excel. The best workaround is to use the ‘Copy All’ command in BO and paste into Excel.
Listserv Archives (BOB member since 2002-06-25)
I have a user that runs a query, clicks on data, then view, then export. He’s trying to export the data to an Excel format. When he
does
so, he receives a “Syntax Error in Field Definiton (3292)” any clues.
There may be other reasons, but I got that error when I went into SQL and renamed one of my fields in the SELECT statement as “Number”. Changing the name eliminated the error. Maybe it’s a reserved word or it’s treating it as a function or something else - I have no access documentation on error messages. Also, I’m running 4.0.5.5 with Oracle, your results may vary with later versions.
If exporting to Excel doesn’t work, I export to Text, change the file extension to ‘xls’ and open the file as Excel anyway. That usually works when exporting to Excel won’t work, but I prefer exporting to Excel, since it puts empty cells out as empty cells, rather than “NULL”, it handles data with double quotes in it a little more gracefully, and it puts out text that is preceded with a dash as text (rather than as a formula). On the down side, it puts out dates as strings, and I have to convert them back to dates, and it sometimes generates strange errors which can lock up BO with ‘illegal operations’. I’m hoping some of this will improve when we start running the next version.
Jack Mathis
MATHISSJ@UCARB.COM
Listserv Archives (BOB member since 2002-06-25)
I’ve had a similar error occur sometimes in 4.1.2 when I use the same column twice in a report and try to export it to Excel. In cases when that happens, I usually export it as a csv and open it up in Excel without problems.
Jim Droppa
Source Consulting
On Mon, 9 Nov 1998 10:32:24 -0500, DEMPSEY.MICHAEL wrote:
Hey Folks…
I have a user that runs a query, clicks on data, then view, then export. He’s trying to export the data to an Excel format. When he does so, he receives a “Syntax Error in Field Definiton (3292)” any clues.
Thanks…
Normal is the average of extremes
Michael Dempsey
Manager, Data Base Administration
University of North Carolina Hospitals
eMail MDEMPSE.ISD1@MAIL.UNCH.UNC.EDU
_______________________________________________________ Get your free, private e-mail at http://mail.excite.com/
Listserv Archives (BOB member since 2002-06-25)
I came across this error a while ago with 4.1.1. After talking with Business Objects support, it turned out to be a known bug. It may have been fixed in 4.1.3, I don’t know. In my case, the problem was that the object names were too long. I don’t remember what the limit was but mine were at or near the maximum length for a name and two of the objects had identical names except for the last character. Two work-arounds were offered: 1) rename the objects to have shorter names or 2) Export the data in “.csv” format. I choose option 2, and the data imported into Excel perfectly.
Dennis Edgecombe
Washington State University
dennis_edgecombe@wsu.edu
Listserv Archives (BOB member since 2002-06-25)