October 8, 2012 at 7:36 am
afternoon all.
We generate a report to XLS format with no header and no footers - just data. The report design shows the page size snapped to the width of the report columns.
When exported to Excel the format opens in excel fine, but we have column DN that is not visible (it's there just so small it's not visible).
Our user then try to import the XLS into MS access, which results in an error along the following lines:
Run-time error '2391':Field 'F118' doesn't exist in destination table '<table name>'.
basically it thinks column DN should contain data.
I can think of how to change the report to resolve the issue.
Anyone had a similiar issue? any ideas how to resolve?
_____________________________________________________________________________MCITP: Business Intelligence Developer (2005)
October 8, 2012 at 7:41 am
So, you just have one table on the report? nothing else?
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
October 8, 2012 at 8:02 am
Although from an operational point of view I would question the wisdom of using SSRS to export to Excel to be imported by Access, the first thing I would try is to export to .csv and then import that into Access.
That said I would probably go directly at the data with Access, rather than the 2 step above. Or, even cut Access out of the equation all together and do your work in SQL Server.
October 8, 2012 at 9:19 am
Hi Daniel - yeah - it's just the one report and I agree - it should just be straight to Access or better still SQL, but hey ho .... thats how the business want to operate.
I'll try csv but I'm keen to find an answer to the problem other than changing format.
thanks for the reply
_____________________________________________________________________________MCITP: Business Intelligence Developer (2005)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply