To cut a long story short:
· We’ve just had our Office install updated to 2010 (although Access remains on Office 2007)
· I have an Excel file “Consents Current Extract.xlsx” which contains data I wish to plot in MapInfo
· When I try to open the file, I get an error:
Microsoft Access Database Engine: The Microsoft Access database engine could not find the object 'Consents Current Extract$'_xlnm._FilterDatabas'. Make sure the object exists and that you spell its name and the path name correctly. If 'Consents Current Extract$'_xlnm._FilterDatabas' is not a local object, check your network connection or contact the server administrator.
Does anyone know why?
Yours,
Martin A Spiers
Senior Engineer
![]()
1 Red Hall Avenue
Paragon Business Village
Wakefield
WF1 2UL
tel. +44 (0) 1924 880837
fax. +44 (0) 1924 880888
email
martin....@mwhglobal.com
No, I don’t know why – but it might be a good idea to see whether Excel will open the sheet. Your error may indicate that the range list filterdatabase is damaged.
Ian Thomas
Scientific Software
Excel can open the file, and there is no defined filter, named ranges, external links or anything else fancy.
I’ve tried with a few other .xlsx files and get the same error message, but I can still open .xls files.
I’m worried that the Office upgrade has broken something.
Martin, I never use Excel data with MapInfo so I wouldn’t know if MI versions can handle the .XLSX (ZIP-format) files, as oppose to the pre-Office2007 .XLS files.
For someone else to help, they might need to know your MapInfo version, and whether you have been successfully opening Excel .XLSX (not .XLS) type files with it, prior to the install of Office 2010.
I have MapInfo v 10.0 build 26, and could open .xlsx files when I had Office 2007.
Yes.
If I save the file as an .xls (97-2003 format); then I can open it.
If I save it as an .xlsx, then I can’t. There isn’t any option to save it as a 2007-format .xlsx, and AFAIK there’s no difference in formats anyway.
Greg Driver
System Administrator
Applications
Support
Support Services - ICT
Surrey
Police
NOT PROTECTIVELY MARKED
Information about this
E-mail
This email and any
files or attachments with it are intended solely for the use of the
individual(s) or organisation(s) to whom it is addressed.
It may contain information that is confidential or
subject to legal and/or professional privilege.
If you have received this
email in error please notify the sender and delete it including any files or
attachments from your e-mail account or computer.
Any opinions expressed
in this email are those of the individual and not necessarily those of Surrey
Police.
Surrey Police monitor incoming and outgoing
e-mail.
If this list can’t find the solution, I’ll throw the problem at our IT helpdesk and they’ll probably reinstall either MapInfo or Office or both.
Yep�
V10.0 came out in 2009 - before the release of Office 2010.Always difficult to be forwardly compatible!!
�
John IeversCDR Group
www.cdrgroup.co.uk
www.browse-a-map.co.uk
Tel: 01433 621282
Fax: 01433 621292
Specialists in Geographic Information Systems
Thanks to everyone who’s trying to help. I’ve done some more testing and will set out everything I’ve found so far:
1. I can’t open any .xlsx files created in Office 2010, but can open them if they were created in Office 2007.
2. I can open .xls files saved from Office 2010
3. My colleague, also using MIv10 and Office 2010, can open the files in MapInfo
4. The only substantive difference between our setups is that I have Access 2007 installed.
5. The error message refers to the Microsoft Access Database Engine. Presumably MI uses this to open the .xlsx files?
Points 4 and 5 above suggest that I should get my install of Access upgraded to 2010. Does anyone know if MI v10 can open Office 2010 version .accdb files or if I’d then need a MapInfo upgrade?
From: mapi...@googlegroups.com
[mailto:mapi...@googlegroups.com] On Behalf Of Uffe Kousgaard
Sent: 17 November 2011 11:51
To: mapi...@googlegroups.com
Subject: Re: [MI-L] Error message when opening .xlsx file in MapInfo 10.0 after installation of Office 2010
XLSX was introduced with Office 2007, so that isn't the issue.
Perhaps saving as XLS solves the problem?
Regards
Uffe Kousgaard
CDR Group wrote:
Yep
V10.0 came out in 2009 - before the release of Office 2010.
Always difficult to be forwardly compatible!!
John Ievers
CDR Group
www.cdrgroup.co.uk
www.browse-a-map.co.uk
Tel: 01433 621282
Fax: 01433 621292
Specialists in Geographic Information Systems
--
You received this message because you are subscribed to the
Google Groups "MapInfo-L" group.To post a message to this group, send
email to mapi...@googlegroups.com
To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching
archives, feature requests, to visit our Wiki, visit the Welcome page at
http://groups.google.com/group/mapinfo-l?hl=en
Yes, I would not expect that (Office 2007 vs 2010) to be a problem.
What was the incremental change between MapInfo 10 and the 10.1 update for?
Ian Thomas
Scientific Software
From: mapi...@googlegroups.com
[mailto:mapi...@googlegroups.com] On Behalf
Of Uffe Kousgaard
Sent: Thursday, November 17, 2011
7:51 PM
To: mapi...@googlegroups.com
Subject: Re: [MI-L] Error message
when opening .xlsx file in MapInfo 10.0 after installation of Office 2010
XLSX was introduced with Office 2007, so that isn't
the issue.
Perhaps saving as XLS solves the problem?
Regards
Uffe Kousgaard
CDR Group wrote:
Yep
V10.0 came out in 2009 - before the release of Office 2010.
Always difficult to be forwardly compatible!!
John Ievers
CDR Group
www.cdrgroup.co.uk
www.browse-a-map.co.uk
Tel: 01433 621282
Fax: 01433 621292
Specialists in Geographic Information Systems
And now I’ve found that if I copy the data into a new .xlsx file, then I can open that in MapInfo.
I’m quite confused.
From: mapi...@googlegroups.com [mailto:mapi...@googlegroups.com] On Behalf Of Martin Spiers
Sent: 17 November 2011 12:02
To: mapi...@googlegroups.com
It might have something to do with the way those particular .xlsx files were created. Were they created on your computer? Did you import data rather than typing it in or using the Clipboard (which is how I guess you "copied" the data into a new worksheet)? Did you use Paste Options to make sure only values were pasted? Was a different template used?
Spencer
There is a whole shopping list of reason why XLSX won’t import
correctly
At the most basic level MAPINFO can only support 255 columns
Microsoft web page
“Specifically, the Office Excel 2007 grid is 1,048,576 rows by 16,384
columns, which provides you with 1,500% more rows and 6,300% more
columns than you had available in Microsoft Office Excel 2003. For
those of you who are curious, columns now end at XFD instead of IV.”
Glen
--
You received this message because you are subscribed to the
Google Groups "MapInfo-L" group.To post a message to this group, send
email to mapi...@googlegroups.com
To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching
archives, feature requests, to visit our Wiki, visit the Welcome page at
http://groups.google.com/group/mapinfo-l?hl=en
Glen
--
You received this message because you are subscribed to the Google Groups "MapInfo-L" group.To post a message to this group, send email to mapi...@googlegroups.com To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching archives, feature requests, to visit our Wiki, visit the Welcome page at http://groups.google.com/group/mapinfo-l?hl=en
"This appears to be based upon the sheet name and renaming it resolves
this problem as a temporary workaround. Whilst I was searching through
our knowledge base I discovered that this is in fact a bug.
Engineering have advised that this issue occurs if a sheet name
contains spaces AND if you have applied filters on the same sheet.
A bug has been created for this issue and as a workaround you can
create a sheet without performing both the steps mentioned above. This
issue does not limit you from creating an excel sheet with filters
over it or an excel sheet with a space in its name but not both of
them together.
When we have been advised of a fix to this issue we shall update you"
This doesn;t quite explain why my colleague could open the file whilst
I can not, but renaming the sheet does work.